Visual Studio 2005 and Intel Fortran 9.1

[hermannl]

Hi all,

I am facing severe trouble when porting a project from Visual Studio.Net 2003 to Visual Studio 2005 and replacing Fortran 9.0 by 9.1 (ia32 version). I have taken the same optimization settings as in VS 2003 and always get an error in multi-file optimization.Regardless of the chosen optimization level (even if Iswitch back to standard optimization level (O2) and deactivate global optimizations) - always the same problem. Thecompiler stopswhenit reachessome memory limit (somewhere around 2 GB, Windows XP 32 bit) and then I get the error message stating some multi-file optimization error. Unfortunately, the same behavior is observed, when I run the compilation under Windows XP x64. My PC has 4 GB RAM, so that shouldn't be the problem (at least under Win XP x64).

Has anyone observed a similar behavior (or better - solved it)? Astoundingly, the program is generated without any problem if I run the compilation and linkage process from the comannd line.

I have not yet tried the x64 setting in VS 2005; no problems are encountered, when the em64t compiler is used in command shell (same compilation/linkage settings).

Best,

Hermann

[Steven_L_Intel1]

The "error in multifile optimization" message is not related to optimization level. This message comes from the Intel pre-linker and USUALLY is accompanied by some other error message about a .obj or .lib file. It could be that it is running out of memory, though, due to a bug.

Please report this problem to Intel Premier Support and attach everything needed to reproduce the problem.

[hermannl]

Dear Steve,

unfortunately there was only the message regarding out of memory problems and no hint to an obj or lib file. And, the problem remained even if I turned off opt. completely.

Finally, and with the help of premier support, I have been able to solve the issue. The project involved consists of Fortran and C++ parts, and in the C++ settings, global opt. has been activated (seems to be a default setting for VS 2005 C++). Taking the RSP files written by VS and using them in a command shell, the problem became obvious. Turning off these global opt in C++ makes everything working fine!

Having solved this, I will try using global opt in the near future (but I guess first using command line mode or Linux).

Best,

Hermann

[arjen_markus1]

I have just run into the same problem using VS 2003:
The Fortran part is a single file and it links against a C library.
It is part of a series of programs and other programs compile and link
without any problem.

I created the project from existing CVF+MSVC 6 projects and used
default options only.

The build is for debugging and there are no optimisations: neither on
the Fortran nor on C side.

How can I solve this problem?

Regards,

Arjen

[arjen_markus1]

Further information (I found that by examining the build report without the interference of the filtering by Visual Studio):

Linking...
Link /OUT:"Debug/Demo_02.exe" /INCREMENTAL /NOLOGO /LIBPATH:"....libwin32_debug" /LIBPATH:"D:libwin32" /DEBUG /PDB:"Debug/Demo_02.pdb" /SUBSYSTEM:CONSOLE kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /MACHINE:I386 /NODEFAULT:libcd
"Debug/Demo_02.obj" "....Debugmylib.lib"
backend signals

Severe: **Internal compiler error: internal abort** 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.

Link: error: problem during multi-file optimization compilation (code 3)
Link: error: problem during multi-file optimization compilation (code 3)


Regards,

Arjen

[Steven_L_Intel1]

Please report this to Intel Premier Support and attach a ZIP of your solution folder.

[hermannl]

Hi Arjen,

may be the following procedure might be of some help.

Start a rebuild of your project and have a look at the (temporary!) files named something like RSP1.RSP, which are located in the Debug or Release directories. I took (copies of) these files and started compilation/linker from the command line, which showed me very fast what was happening and so I could solve my problem (at least for the moment).

Best,

Hermann

[Steven_L_Intel1]

Arjen sent me his project. The problem seemed to be a line-feed character inserted by the "extract CVF project items" wizard into the "additional command options" for the linker at the end of the line. (Showed as a square box in the IDE.) Deleting that made the "internal compiler error" go away (the error was coming from the Intel pre-linker xilink, not the compiler itself.)

I haven't heard from him yet as to whether that completely solved the problem.

[arjen_markus1]

I can confirm now that _somehow_ this was the problem.

I could not see any special or weird character in my version of the IDE,
but there was a linefeed/newline in the text box. When I removed it, the whole
option was ignored though.

My solution then was to set the option "ignore specific library" under the
category Linker/Input to "libcd" and then it worked. I do not know why
the other projects do work, so that remains a mystery ...

Regards,

Arjen

[jimdempseyatthecove]

Arjen,

??"Debug/Demo_02.obj" "....Debugmylib.lib"

Did you edit the above line sniped from your build report?

IOWare the "...." in your build? ("....Debugmylib.lib")

If so, then there may be a problem in parsing the file specification.

I used to have a similar problem when trying to specify multiple paths (specifying module paths) which resulted in creating a folder named ";Debug" (semicolon in directory name).

The "...." (if in your build) may be causing similar problems.

Jim Dempsey

[arjen_markus1]

Hi Jim,

I do not remember, but I think it is very likely that I did edit this
piece of the text. (I typically use four periods when removing
a directory like that ...)

Anyway, the cause of the problem was identified and the project
compiles and links as it should.

Thanks for your reply - Visual Studio 2005 is a new environment
for me and I am not sure I like it ;)

Arjen

[jimdempseyatthecove]

Arjen,

What do you best like about VS 2005 over VS 2003?

Currently I run on a 4-core Opteronsystem using Windows XP Pro (32-bit). 2GB is sufficient for my application. Other than for lack of NUMA support I find little incentive to migrate to Windows ?? 64-bit O/S and VS 2005. In your opinion is there some non-obvious reason to do so?

Jim Dempsey

[bbaadre1975]

DEAR SIRS

For our work purpose, we have to use Intel Fortran Visual Compiler 9.1 together with ADINA8.5 software. unfortunately, we could not find this version of fortran anywhere.

Is it possible for us to get Intel Fortran Visual Compiler 9.1 from you
we look forward to receiving your kind advice.
Prompt response is highly appreciated
thank you
BADREDDIN
UNIVERSITI REKNOLOGI MALAYSIA

[Steven_L_Intel1]

BADREDDIN,

Purchase a license for the current versiion. You can then download and install an older version by following these instructions.