Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

Still having compiler problem

Anne_Stewart
Beginner
1,267 Views
I am still getting this error:

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

when trying to compile legacy code on the 11.0.074 compiler. I'm attaching all the source code (zipped). Hope you can help. Thanks.
0 Kudos
1 Solution
Steven_L_Intel1
Employee
1,267 Views
It's further down on that page.

View solution in original post

0 Kudos
7 Replies
Steven_L_Intel1
Employee
1,267 Views
I can reproduce the problem. Workaround: Project > Properties > Fortran > Diagnostics. Set Check Routine Interfaces to No.
0 Kudos
Steven_L_Intel1
Employee
1,267 Views
The upcoming 11.1 (late June) also appears fine, even with Check Routine Interfaces on.
0 Kudos
Anne_Stewart
Beginner
1,267 Views
I can reproduce the problem. Workaround: Project > Properties > Fortran > Diagnostics. Set Check Routine Interfaces to No.

This is great news. However, I can't find a check routine interfaces in the diagnostics. I set generate interface blocks to "no", that is the only mention of interfaces in the diagnostics window. The code will still not compile with this change, however.
0 Kudos
Steven_L_Intel1
Employee
1,268 Views
It's further down on that page.

0 Kudos
Anne_Stewart
Beginner
1,267 Views
Hi Steve,

First, thanks for your rapid responses. Following your first reply yesterday, I changed some flags in diagnostics and anywhere else that looked promising, and rebuilt, and the code is finally compiling. You Intel folkshave beensuperb with your help in getting thisworking, and I really appreciate it. I am still pretty new at Fortran andcompletely new tothe Intel versionand your support pages here, and apologize for anyunnecessary run-around I've inadvertently given you folks.

FYI My diagnostics window does not havethe multiple options in your reply. It has only one option, if Iapply the +: Compile Time Diagnostics, which I selected as show all/warn all. I am running on VS2005, which may account for the difference.

Cheers!

Anne


0 Kudos
Steven_L_Intel1
Employee
1,267 Views
Hmm - might be a compiler version difference. Check under External Routines to see if it shows up there.

You haven't given us any "run-around", and we apologize for the compiler bugs getting in your way.
0 Kudos
Anne_Stewart
Beginner
1,267 Views
The rest of the diagnostic optionstoggleas I switch the setting in the configuration pull down menu from debug torelease - this is only happening in files with the troublesome code though. Also, I think Ifirst changed the configuration in the solution configurations window in the top toolbar.Anyway, I see by adjusting the configuration settings how to get tothose options in the future.

I've been able to compile the code several times now, and theexecutableisworking (with no more problems thanusual) so I think I'm in the clear.

Thanks for all the help!

Anne

0 Kudos
Reply