Aborting due to internal error

[Rob_Redmon]

I'm running into an "Aborting due to internal error" while trying to building a Fortran only application using the IDE. The build process using the IDE is failing on the file named RSDENA_EXB.FORwhile a command line attempt to compile this file appears to work fine:

Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files>"C:\\Program Files\\Intel\\ComposerXE-2011\\bin\\ia32"\\ifort.exe /c RSDENA_EXB.FOR

Intel Visual Fortran Compiler XE for applications running on IA-32, Version 12.0 Build 20110112

Copyright (C) 1985-2011 Intel Corporation. All rights reserved.

Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files>

The Build log for the IDE build attempt follows:

Compiling with Intel Visual Fortran Compiler XE 12.0.2.154 [IA-32]...

ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\Photoel-Freqs.FOR"

ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-MSIS00\\MSIS00-SUBS.FOR"

ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\RSSUBC.FOR"

ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\IN_OUT.FOR"

Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\IN_OUT.FOR(42): warning #6371: A jump into a block from outside the block may have occurred. [80]

IF (CH_ARRAY(J:J).NE.' ') GO TO 80

-----------------------------------------------------^

Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\IN_OUT.FOR(143): warning #8042: This argument must be of type character of length 1. [NEWCHAR]

DIGIT=ICHAR(NEWCHAR)-48

--------------------^

ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\AURSUB.FOR"

ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\RSDENA_EXB.FOR"

Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\RSDENA_EXB.FOR(389): internal error: Please visit 'http://www.intel.com/software/products/support' for assistance.

IF(J.LT.JEQ) CALL TERMID(J,BB,C,A,DS(J-1),DS(J),QL,QM,QU)

^

[ Aborting due to internal error. ]

compilation aborted for Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\RSDENA_EXB.FOR (code 1)

FLIP-MSIS00_WIN - 1 error(s), 2 warning(s)

Compiling with Intel Visual Fortran Compiler XE 12.0.2.154 [IA-32]...ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\Photoel-Freqs.FOR"ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-MSIS00\\MSIS00-SUBS.FOR"ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\RSSUBC.FOR"ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\IN_OUT.FOR"Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\IN_OUT.FOR(42): warning #6371: A jump into a block from outside the block may have occurred. [80] IF (CH_ARRAY(J:J).NE.' ') GO TO 80-----------------------------------------------------^Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\IN_OUT.FOR(143): warning #8042: This argument must be of type character of length 1. [NEWCHAR] DIGIT=ICHAR(NEWCHAR)-48--------------------^
ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\AURSUB.FOR"ifort /nologo /debug:full /Od /warn:interfaces /module:"Debug\\\\" /object:"Debug\\\\" /Fd"Debug\\vc90.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc9 /Qlocation,link,"c:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\\\bin" "Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\RSDENA_EXB.FOR"Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\RSDENA_EXB.FOR(389): internal error: Please visit 'http://www.intel.com/software/products/support' for assistance. IF(J.LT.JEQ) CALL TERMID(J,BB,C,A,DS(J-1),DS(J),QL,QM,QU)^[ Aborting due to internal error. ]compilation aborted for Z:\\work\\FLIP_WIN\\trunk\\SOURCE-files\\FLIP\\FLIP-common-files\\RSDENA_EXB.FOR (code 1)

FLIP-MSIS00_WIN - 1 error(s), 2 warning(s)

[mecej4]

>"The build process using the IDE is failing on the file named RSDENA_EXB.FORwhile a command line attempt to compile this file appears to work fine:"

There is not much to be surprised at here, since is is probable that the compiler options used in the IDE differed from those used at the command line. Check and let us know the options used.
-------xx-------
You have not shown the source, so we do not know what caused these two warning messages:

warning #6371: A jump into a block from outside the block may have occurred.

warning #8042: This argument must be of type character of length 1

Until known/shown to be benign, warnings should be taken as indicative of the presence of errors in the source.

> [ Aborting due to internal error. ]

This should never happen, but until we have perfect compilers we shall see this message. Fixing it, however, requires that the compiler writers reproduce the error. That again requires that the user provide source code, information about the OS and compiler, possibly data files, and sufficiently complete instructions.

[Steven_L_Intel1]

Please provide the source file and any include or module sources it needs, and we'll be glad to take a look. You may want to first install Update 3 and see if the problem remains in that update.

You may find that setting the option Diagnostics > Check Routine Interfaces to "No" eliminates the error. This should be a temporary workaround only.

[jeremy_h]

I've seen this "abort with internal error" when I switched back and fore between 11.1 and XE2011 without cleaning.

[Steven_L_Intel1]

That's a very generic message that says the compiler is confused. It can have many causes. I would not expect this just by switching compiler versions and perhaps using a .mod file from a newer version, but that's possible. We need a test case in order to investigate and suggest workarounds.

[mecej4]

I am unable to reproduce the error shown in the log file of your most recent post. File RVN2PB.FOR compiled with no errors using the same options that you used.

The log file indicates that your Debug directory may have contained some *__genmod,f90 and *.mod files that were incompatible with the 12.0.2 compiler. Please delete all generated files in that directory and try again.

[Steven_L_Intel1]

Right click on the Fortran project, select Properties. Select Fortran > Diagnostics. Scroll down and set "Check Routine Interfaces" to "No". Then rebuild the project. This is simply a suggestion to see if that is the trigger.

As for getting Update 3, I'd suggest waiting for Update 4 on Thursday or Friday. If you did not check the box to request support when you got the evaluation copy, go to the Intel Registration Center, register your evaluation serial number and check the box for support. You can then log in to the Registration Center and download any compiler released during your trial period.

[Rob_Redmon]

@mecej4:

Good idea. I tried your idea but alas it was not the problem.

@Steve:

Setting "Check routine interfaces" to NO worked, i.e. I was able to create an executable. (It doesn't do quite what I think it should do but perhaps I'll have to take that up with the developer.) Note that in order to set this diagnostic property, setting it for the project was not enough; i.e. each source file's property was not respecting the project default. Thus I had to highlight all ~50 source files, right click and set the property that way. I can confirm that this flag is related to the "internal error" trigger for failure for ~20 fortran source files.

Would you mind explaining more or less what this diagnostic flag does and why it should be set to yes versus no?

Thanks for the update guidance. I'll look for an update later this week.

[Steven_L_Intel1]

This option checks for consistency between calls and called procedures across source files in the absence of explicit interfaces. It's a wonderful diagnostic tool, but over the years that we've had it it sometimes triggers compiler errors. Yours is one such case. Please try again with Update 4 which should be out soon. If it fails there with this option enabled, please let us know.

I am surprised that changing the project property wasn't enough.