different results using Intel Visual Fortran for Windows and ifort for Linux

[Vitaliy_R_2]

Hi, everybody
I have one scientificproject (band structure calculation)which was compiled in MSVS 2008 with IVF 11.1.051 - options were used by default, the RELEASE application was obtained and it works perfect.
But now I am migrating to Linux (ifort version 11.1), there the program compiles without any error, but when I give the application the same data as in Windows - I get completely different results. I am sure for 99% that there are some compiler options in IVF, but I don't know where they are (I was looking in Project Properies - iFort - Command Line) and was confused, because their format differ from those I usually use in Linux.
The command line in IVF:
/nologo /module:"Release\\\\" /object:"Release\\\\" /libs:static /threads /c
In linux I use makefile, so the question is - what should write for theFLAG option in makefile, how to convert those "keys" into linux format?
There are lots of options in IVF, does ifort really use only those in Command Line?

On my opinion there is a problem with fp calculation, but all flags that make it more precise in linuxproduce the same wrong result.

Thanks

[mecej4]

There is a section in the Intel Fortran documentation that gives you a list of compiler options and their meanings. For each option, the variants for the three target operating systems (Windows, Linux, OSX) are given. You could use that information to check that you use the correct Linux equivalents of the options you used on Windows.

The options are generally identical, except that for each option under Linux (i) the the leading / is replaced by -, (ii) if the next letter is Q, it is dropped, and (iii) : is replaced by a space.

[TimP]

If you use -fp-model source, the Windows spelling is /fp:source
-assume protect_parens is nearly the same: -assume:protect_parens

The linux -m options are spelled in Windows with /arch: e.g. /arch:SSE3

On either linux or windows, ifort -help should assist you quickly in finding those options. The html docs give both spellings.