**Internal compiler error: internal abort** in ifort v12 when using STRUCTUREd RECORD in VOLATILE COMMON

[vrws]

Hi everybody,

we experience big problems with the new version of ifort [(IFORT) 12.1.4 20120410] with codes using STRUCTUREd RECORDs in VOLATILE COMMON. In version 11 this worked OK.

The following code sequences are minimum examples to show the problem:
[cpp] PROGRAM CompTest IMPLICIT NONE STRUCTURE /MyStruct/ INTEGER *4 MyArray (20) END STRUCTURE RECORD /MyStruct/ MyRecord (10) COMMON /MyTest/ MyRecord VOLATILE /MyTest/ MyRecord(5).MyArray(7) = 1 END [/cpp] ifort -o comptest.o comptest.for
produces a catastrophic error:

LOC_type is: 1
101000_1

: 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.
compilation aborted for comptest.for (code 1)

The following code
[cpp] PROGRAM CompTest IMPLICIT NONE STRUCTURE /MyStruct/ INTEGER *4 MyArray (20) END STRUCTURE RECORD /MyStruct/ MyRecord (10) COMMON /MyTest/ MyRecord VOLATILE /MyTest/ CALL Sub (MyRecord(5).MyArray(7)) END [/cpp]
ifort -o comptest.o comptest.for
gives

0_1529

comptest.for(11): 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.
compilation aborted for comptest.for (code 1)

In this case there is a line number [11: CALL Sub (MyRecord(5).MyArray(7))] but no more reasoning.

Any idea what goes wrong here?

Volker

[Steven_L_Intel1]

The VOLATILE on the COMMON seems to be triggering this. It compiled ok in 12.0.5 but not any 12.1 compilers. You can work around it by compiling this source with optimization disabled. We'll have the developers take a look.

[Anonymous66]

Hello Volker,

I have escalated this issue to the developers. The issue number is DPD200232977. I will post any updates on this issue to this thread.

Regards,
Annalee

[vrws]

Hello Steve & Annalee,

thanks a lot for your ultra fast responses and escalation of our problem!

We like this very much as this is surely the best help one can expect,

Volker

[Anonymous66]

Hello Volker,

We are currently planning to include a fix for this issue in a release scheduled for later this year.

Annalee

[Anonymous66]

This is issue has been fixed in Intel® Fortran Composer XE 2013 which is now available at the Intel® Registration Center. Regards, Annalee Intel Developer Support