[MITgcm-support] linux_ia32_ifort

[Patrick Heimbach]

Hi Dimitris,

I've used ifort 8.0.066 on the  columbia2 and the GFDL altix
(see e.g. 'module avail' on columbia2)
I have changed -DWORDLENGTH=4 to -DWORDLENGTH=1
but didn't need the -assume byterecl.
So I guess these two are equivalent ways, i.e.
either do the -DWORDLENGTH=1 or the -assume byterecl
Not sure whether one is preferable in terms of performance?

Cheers
-Patrick

PS: 
I need to use ifort 8.0 for the line search, the
ifort 7.... doesn't allow large enough array/vector sizes.



On Monday 27 September 2004 14:26, Dimitris Menemenlis wrote:
> Ed, the following changes appear to be needed in linux_ia32_ifort
> for ifort 8.0.  Anyone else using ifort 8.0 succesfully with original
> linux_ia32_ifort ?
>
> D.
>
> #!/bin/bash
> #
> #  Ed Hill
> #
> #  tested on faulks, 20030818
> #
> #  Build options for the intel 8.0 fortran compiler
> #  the compiler is now called ifort (not ifc) and it appears to
> #  need -DWORDLENGTH=1 and not -DWORDLENGTH=4
> #  (which is what ifc 6.0) used to have.
>
>
> CPP='/lib/cpp  -traditional -P'
>
> #  Note that the -mp switch is for ieee "maintain precision" and is
> #  roughly equivalent to -ieee
> if test "x$IEEE" = x ; then
>     FFLAGS='-132 -r8 -i4 -w95 -W0 -WB -assume byterecl'
> else
>     FFLAGS='-mp -132 -r8 -i4 -w95 -W0 -WB -assume byterecl'
> fi
>
> FOPTIM='-O3 -align'
> #P3  FOPTIM     = ( $FOPTIM '-tpp6 -xWKM' )
> #P4  FOPTIM     = ( $FOPTIM '-tpp7 -xWKM' )
>
> FC=ifort
> DEFINES='-D_BYTESWAPIO -DWORDLENGTH=4'

-- 
----------------------------------------------------------
Patrick Heimbach     Massachusetts Institute of Technology
FON: +1/617/253-5259                    EAPS, Room 54-1518
FAX: +1/617/253-4464               77 Massachusetts Avenue
mailto:heimbach at mit.edu                 Cambridge MA 02139
http://www.mit.edu/~heimbach/                          USA