ICE depending on the time stamp of ifort-11

[lcoul]

trouble with ifort-11 when compiling a program with specific options :

sade{coul} 21 : ifort -c -g -openmp -zero -fpe0 -fltconsistency sparse_matrix.f90
sparse_matrix.f90(516): (col. 11) remark: OpenMP DEFINED LOOP WAS PARALLELIZED.
sparse_matrix.f90(525): (col. 11) remark: OpenMP DEFINED LOOP WAS PARALLELIZED.
0_1855

: catastrophic error: **Internal compiler error: internal abort** 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.
in file sparse_matrix.f90, line 516, column 31

compilation aborted for sparse_matrix.f90 (code 3)
sade{coul} 22 : ifort --version
ifort (IFORT) 11.0 20090318
Copyright (C) 1985-2009 Intel Corporation. All rights reserved.

But if I compile the same program, with the same options, using ifort (IFORT) 11.0 20090131, then all is OK.

[Steven_L_Intel1]

I have reported this to the developers - the issue ID is DPD200139790. It seems to relate to naming ROW in the PRIVATE clause where ROW is a POINTER to type ROW_TYPE.

[lcoul]

Quoting - Steve Lionel (Intel)

I have reported this to the developers - the issue ID is DPD200139790. It seems to relate to naming ROW in the PRIVATE clause where ROW is a POINTER to type ROW_TYPE.

Three additional questions :
- is that trouble already solved in a more recent version ?
- is the object file correctly generated when the compile phase is OK (for instance in omitting the compilation option -g)?
- how to follow the issue ID you have provided?

Thank you in advance

Franois Jacq (alias lcoul or FJ depending on the forum)

[Steven_L_Intel1]

The problem is not yet fixed - I will update this thread when there is news about the issue. On review, omitting -g may not help you, but you can try it. It seems more tied to the optimization level - with optimization disabled, as it is with -g, I see the error. Sometimes with optimization enabled, I don't.

[Steven_L_Intel1]

This bug has been fixed in our sources. The fix is expected to be in Update 4, planned for the second half of December.

[Steven_L_Intel1]

This issue is resolved in Update 4, available now.