Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

argument mismatch

clang001
Beginner
1,368 Views
I just switched over to Intel Visual Fortran 9.1 from CVF and I noticed that I no longer receive link warnings when the number of arguments in the call statement does not match the number of arguments in the subroutine statement. Is there a switch somewhere that will help me identify these coding errors?
0 Kudos
5 Replies
Steven_L_Intel1
Employee
1,368 Views
Yes, there is. Two switches you need to use together:

/gen_interfaces /warn:interface

The Intel compiler uses the C calling mechanism by default, which doesn't use the @n suffix on routine names.

Please be sure to read Porting Applications to Intel Visual Fortran from Compaq Visual Fortran.

For technical support, please see this support FAQ.
0 Kudos
clang001
Beginner
1,368 Views

Steve, thank you for the quick response. Before I dig any further, are there any obvious reasons why I'm getting the following error when I turn on those switches?

------ Build started: Project: swt2k, Configuration: Debug|Win32 ------


Deleting intermediate files and output files for project 'swt2k', configuration 'Debug|Win32'.

Compiling with Intel Fortran 9.1 C:Program Files (x86)IntelCompilerFortran9.1IA32...

ifort /nologo /Zi /Od /gen-interfaces /warn:all /real_size:64 /align:dcommons /module:"Debug/" /object:"Debug/" /traceback /check:bounds /RTCu /libs:static /threads /dbglibs /c  /extfor:f /Qvc8 /Qlocation,link,"C:Program Files (x86)Microsoft Visual Studio 8VCin" "D:userslangevinseawat2kswt2000sourcev3_14_20060609Sourceutl6.f"

fortcom: Fatal: There has been an internal compiler error (C0000005).
Severe: **Internal compiler error: segmentation violation 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.

compilation aborted for D:userslangevinseawat2kswt2000sourcev3_14_20060609Sourceutl6.f (code -1073741819)




swt2k build failed.



0 Kudos
Steven_L_Intel1
Employee
1,368 Views
We had some problems with that feature in earlier updates. Please make sure that you are running 9.1.025 (current version as I write this.)

To download 9.1.025, log in to the Intel Registration Center and select product Downloads. (For other readers - this is a new method of downloading and you are welcome to try it as well.)
0 Kudos
clang001
Beginner
1,368 Views

FYI--even after grabbing 9.1.025, this feature still does not seem to be working correctly. I sent my files to software support.

The compiler seems to freeze while creating the interface files. The strange thing is, it doesn't freeze for all of them. I can compile some files individually, and it works fine. For other files, the compiler appears to lock up. When the compiler freezes, no progress stops, but the compiler process continues to use the cpu--strange.

0 Kudos
Steven_L_Intel1
Employee
1,368 Views
Thanks, please do report this. the symptom you're seeing is similar to other reports we've had in the past, but the cause isn't always the same.

BTW, we'll have a new update out early next week.
0 Kudos
Reply