- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just attained trial copies of Intel Visual Fortran Composer XE 2011
and VS2010 in order to evaluate the compiler for use at my company on
Windows 7 (32-bit). I tested a simple code and was able to get successful compilation and execution.
I have now moved to testing existing code (.for extensions) in the Intel Visual Fortran Composer XE 2011/VS2010 paradigm. (up until now, the code has been being compiled in a Compaq VF6/Developer's Studio paradigm). The code will not compile saying it fails to compile at Line 1. The BuildLog.htm is below:
The debug folder contains a *_genmod.mod file and a *_genmod.f90 file for each subroutine or function *. I've read some inquiries like this one but cannot figure out proper corrective action. If its relevent, I have turned on VMS Compatibility, F77 Run-Time Compatibility, and F77 Integer Constants.
I have now moved to testing existing code (.for extensions) in the Intel Visual Fortran Composer XE 2011/VS2010 paradigm. (up until now, the code has been being compiled in a Compaq VF6/Developer's Studio paradigm). The code will not compile saying it fails to compile at Line 1. The BuildLog.htm is below:
Compiling with Intel Visual Fortran Compiler XE 12.0.1.127 [IA-32]... |
The debug folder contains a *_genmod.mod file and a *_genmod.f90 file for each subroutine or function *. I've read some inquiries like this one but cannot figure out proper corrective action. If its relevent, I have turned on VMS Compatibility, F77 Run-Time Compatibility, and F77 Integer Constants.
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok. This is a compiler bug and I think it's one that is fixed in the upcoming Update 2. As a workaround, set the option Fortran > Diagnostics > Check Routine Interfaces to "No".
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
These are "generated interface" files created when the /warn:interface ("Check routine interfaces") option is on. You do not need to do anything with these files.
It looks as if you tried to insert a command line switch into a source file. Those don't belong there. The error is at line 38 in driver_v4.for.
It looks as if you tried to insert a command line switch into a source file. Those don't belong there. The error is at line 38 in driver_v4.for.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I may have lost my opportunity for feedback -- I inserted the wrong BuildLog. Below is the proper BuildLog:
This occurs only after inserting a "call" command for one of the subroutines/functions.
Compiling with Intel Visual Fortran Compiler XE 12.0.1.127 [IA-32]...
ifort /nologo /debug:full /Od /vms /f77rtl /intconstant /warn:interfaces /real_size:64 /module:"Debug\" /object:"Debug\" /Fd"Debug\vc100.pdb" /traceback /check:bounds /libs:static /threads /dbglibs /c /Qvc10 /Qlocation,link,"C:\Program Files\Microsoft Visual Studio 10.0\VC\\bin" "C:\Users\Kyle Schmitt\Documents\Visual Studio 2010\Projects\Console1\Console1\driver_v4.for"
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
GEM_LO_GET_LOCATOR_INFO: zero locator value
\Console1\driver_v4.for: catastrophic error: **Internal compiler error: abort signal raised** 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.
\Console1\driver_v4.for (code 1)
Console1 - 1 error(s), 0 warning(s)
This occurs only after inserting a "call" command for one of the subroutines/functions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok. This is a compiler bug and I think it's one that is fixed in the upcoming Update 2. As a workaround, set the option Fortran > Diagnostics > Check Routine Interfaces to "No".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you. That did it.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page