topic ICE on ALLOCATE with undeclared components in Intel® Fortran Compiler

ICE on ALLOCATE with undeclared components

joseph_battelle — Sat, 26 Jun 2010 02:31:59 GMT

Allocating an undeclared type/component turns into an internal compiler error with the current compiler. Steve, what is the difference between an "internal compiler error" and a fatal, "catastrophic" error (as reported previously)? For invalid code such as this, do you want defect reports on internal compiler errors? The catastrophic error is accompanied by a message to report the defect. Plain-old "internal compiler errors" are not.

[fortran]module m7
contains
    function pair_ci
        !allocate(a, source = c) !warning about no explicit type as your would expect           
        allocate(a % x, source = c) !reasonable errors then: fortcom: Fatal: There has been an internal compiler error (C0000005).           
    end function pair_ci
end module m7[/fortran]

ICE on ALLOCATE with undeclared components

Steven_L_Intel1 — Sat, 26 Jun 2010 10:36:07 GMT

"Internal compiler error" is usually when the compiler detects a problem using a code test. The "catastrophic" error is usually an exception such as an access violation, as in your case, that got trapped by a signal handler.

We always want such reports - the compiler should never just die on an invalid program. Thanks.

ICE on ALLOCATE with undeclared components

Steven_L_Intel1 — Mon, 28 Jun 2010 18:17:08 GMT

Issue ID is DPD200157390.

ICE on ALLOCATE with undeclared components

Steven_L_Intel1 — Tue, 20 Dec 2011 20:58:36 GMT

This was fixed in Composer XE 2011 Update 6.