translating intel fortran flags to gfortran

[Tom Roche]

Tom Roche Mon, 14 Nov 2011 13:25:31 -0500
>> I'm recompiling code with gfortran that has previously been done
>> (and is almost entirely documented) using ifc. I have a
>> general question and a specific one:

>> * Are there useful references for translating ifc flags to gfortran,
>>   e.g., a guide to porting?

Tobias Burnus Mon, 14 Nov 2011 20:04:25 +0100
> Not really. Looking at both the ifc/ifort documentation and at the 
> gfortran [1] and gcc [2] documentation seems to be the only way.

http://gcc.gnu.org/onlinedocs/gfortran/Invoking-GNU-Fortran.html

is indeed quite helpful. Why doesn't Intel have something like that?
The best source I've found for ifc (which I don't have installed) is

http://software.intel.com/file/6335
> Intel(R) Fortran Compiler Options

>> * What would be the gfortran equivalent of

>> > -extend_source 132 -cm -w95 -c

> For "-c" use "-c". For "-extend_source 132" use -ffixed-line-length-132.

> -w95 and -cm seem to be warning related. You might simply leave them out 
> (and ignore the warnings). Or use GCC's "-w" to disable all warnings.

Thanks: what (apparently) worked to compile that (which I haven't run
yet--I've got a lotta build dependencies to work through first) was

-ffixed-line-length-132 -w -c

The next item I hafta recompile used ifc flags=

-extend_source 132 -vec-report0 -cm -w95 -c

not all of which is common with the previous. I note

http://software.intel.com/file/6335 p511
> vec-report, Qvec-report
> Controls the diagnostic information reported by the vectorizer.
...
> Arguments
> n Is a value denoting which diagnostic messages to report. Possible values are:
> 0 Tells the vectorizer to report no diagnostic information.

So is there a gfortran equivalent for 'vec-report', or 
should I just ignore it?

Your assistance is appreciated! Tom Roche <Tom_Roche@pobox.com>