topic Re: fortcom: Fatal: There has been an internal compiler error ( in Intel® Fortran Compiler

fortcom: Fatal: There has been an internal compiler error (C0000005).

aliwin — Mon, 17 Aug 2009 12:35:35 GMT

Hi,

I'm getting the following compiler error:
Compiling with Intel Visual Fortran 11.0.074 [IA-32]...
read_orbit_sit.for
fortcom: Fatal: There has been an internal compiler error (C0000005).
From an old posting, looks like it's compiler bug ..?
Any idea how I can avoid this error with IVF 11.0 ?

Thanks,
Ali

Re: fortcom: Fatal: There has been an internal compiler error (

bmchenry — Mon, 17 Aug 2009 13:33:39 GMT

You'll need to provide some sample code that when compiled produced that error for recommendations on eliminating it. Thereare a plethora of reasons why that error may come up, some due to compiler issues, some due to coding problems.

Re: fortcom: Fatal: There has been an internal compiler error (

Steven_L_Intel1 — Mon, 17 Aug 2009 13:34:24 GMT

That error message can have many possible, unrelated causes. It is always a compiler bug, but not always the same one! Can you attach a short (if possible) source file that gets this error, along with the command line used to do the compile?

For more information, see the Knowledge Base article Internal Compiler Error

Re: fortcom: Fatal: There has been an internal compiler error (

aliwin — Mon, 17 Aug 2009 16:17:26 GMT

Quoting - Steve Lionel (Intel)

Thank you Steve & all for your input,

It's the fact that I commented the only existing 2 lines inside an "IF" statement that caused this compiler error.
When I commented the "IF" and "ENDIF" lines the compile went fine.

Regards,
Ali

Re: fortcom: Fatal: There has been an internal compiler error (

Steven_L_Intel1 — Mon, 17 Aug 2009 16:35:46 GMT

Would you please attach the source file? You should never get an internal compiler error, even if you have a syntax error in your source. I want to make sure we fix the compiler bug.

Re: fortcom: Fatal: There has been an internal compiler error (

aliwin — Mon, 17 Aug 2009 17:22:34 GMT

Quoting - Steve Lionel (Intel)

Would you please attach the source file? You should never get an internal compiler error, even if you have a syntax error in your source. I want to make sure we fix the compiler bug.

I don't think it's a syntax error to have an IF block without any instruction inside it, eventhough it doesn't make sense to have this code (and it shouldn't exist).
The file I had this "issue" with is over 500 lines. I tried to keep just the lines that caused the compiler error but the problem wasn't reproducible. Unfortunately I can't send the file without breaking the "Reserved Rights". I tried other combinations to reproduce the problem but wasn't successful.

Re: fortcom: Fatal: There has been an internal compiler error (

Steven_L_Intel1 — Mon, 17 Aug 2009 17:28:30 GMT

You are correct - an IF construct does not require any executable statements inside it.

If you can find a way to provide us with a test case, we'd really appreciate it.

Hi Steve,

antony_muthu__Anto_J — Wed, 19 Feb 2014 13:10:18 GMT

Hi Steve,

I have find the same error that aliwin found some time ago.

I've got:

Intel(R) Visual Fortran Compiler Professional for applications running on IA-32,

fortcom: Fatal: There has been an internal compiler error (C0000005).

The code I am having the error with is FAST by NREL. The code is opensource and can be downloaded from http://wind.nrel.gov/designcodes/simulators/fast/alpha/ It comes with a Visual Studio project and a .bat that can be used to compile it. They say they have compiled their code with Intel® Visual Fortran Compiler XE 12.1.3.300 [IA-32]. I have compiled the previous version of FAST with the Visual Fortran V11.0.075.

Any idea how I can avoid this error with IVF 11.0 ?ç

Thanks,

Jose.

Jose,

Kevin_D_Intel — Wed, 19 Feb 2014 16:59:43 GMT

Jose,

The internal error you and others experienced may not share the same root cause. It is an indicator of an internal failure within the compiler but unless the code you and others compiled is the same or shares something in common it is likely the root causes are different.

The 11.0 release is very old at this point. I will download your code and see whether I can offer any help avoiding it and whether this is already fixed in our latest 14.0 compiler version.

Please stand by...

Sorry, 11.0 is no longer

Steven_L_Intel1 — Wed, 19 Feb 2014 17:02:09 GMT

Sorry, 11.0 is no longer supported and I won't be able to try to find a workaround for you. Please keep in mind that "Internal compiler error" is a very generic error that can have countless causes.

What I usually do when trying to track down one of these issues is selectively commenting out code in the offending source until I find the minimum I need to reproduce the error. That can sometimes give me a clue as to what I might be able to change to do differently, but this is not always possible.

Jose,

Kevin_D_Intel — Sat, 22 Feb 2014 12:11:18 GMT

Jose,

Here is a mockup reproducing test case that I distilled from the FAST code that suffers the internal error. The internal error occurs in relation to LEN(message) in the message2 declaration and the variable's use in the contained subroutine.

SUBROUTINE FOO( message )
CHARACTER(*) :: message
CHARACTER(LEN(message)) :: message2

   CONTAINS
      SUBROUTINE BAR()
         CALL A_MESSAGE(message2)
      END SUBROUTINE BAR
END SUBROUTINE FOO

There is no convenient work around available because this sort of usage appears throughout the original source. Your best course of action to resolve this error is to upgrade to at least the Intel® Visual Fortran Compiler XE 12.1.3.300 [IA-32] version NREL notes using for FAST. The internal error is fixed in that version.