- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When compiling lapack's dpftri source from [1] with the following options with ifort 14.0.3 I encounter an internal compiler error.
$ cd /tmp $ wget -O - http://www.netlib.org/lapack/lapack-3.5.0.tgz | tar -xzf - lapack-3.5.0/SRC/dpftri.f $ ifort -check uninit lapack-3.5.0/SRC/dpftri.f lapack-3.5.0/SRC/dpftri.f: catastrophic error: **Internal compiler error: segmentation violation signal raised** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error. compilation aborted for lapack-3.5.0/SRC/dpftri.f (code 1)
The error goes away when I add -O0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for notifying us about this internal error. I reproduced the error with the latest Composer XE 2013 SP1 Update 4 (14.0 compiler) and the Intel Parallel Studio XE 2015 (15.0 compiler) releases.
As you noted the error is avoidable with -O0. It is also avoidable by removing -check uninit.
I reported this to Development (see internal tracking id below).
(Internal tracking id: DPD200360830)
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for notifying us about this internal error. I reproduced the error with the latest Composer XE 2013 SP1 Update 4 (14.0 compiler) and the Intel Parallel Studio XE 2015 (15.0 compiler) releases.
As you noted the error is avoidable with -O0. It is also avoidable by removing -check uninit.
I reported this to Development (see internal tracking id below).
(Internal tracking id: DPD200360830)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does -check uninit work at -O0?
I filed an issue years ago about the problems of -check uninit when combined with -openmp. It was never answered, to my knowledge.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I honestly don't know. The bug occurs in a code that includes all of LAPACK for debugging purposes and platforms that miss some recent functions in their optimized versions but does not actually call dpftri, so the object gets discarded at the link step. On the machine in question I just turned -check uninit off for dpftri and didn't bother trying the full source with -O0.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page