[MITgcm-support] convincing compiler of node memory size

[Oliver Jahn]

Hi Holly,

the current optfile has the correct options for big executable at the 
end (commented out):

http://mitgcm.org/viewvc/MITgcm/MITgcm/tools/build_options/linux_amd64_ifort%2Bmpi_ice_nas?hideattic=0&revision=1.1&view=markup

#- For really big executable (> 2 GB), uncomment following 2 lines
#FFLAGS="$FFLAGS -mcmodel medium -shared-intel"
#CFLAGS='-mcmodel medium'

Oliver


On 04/15/2010 11:14 AM, Martin Losch wrote:
> Hi Holly,
>
> usually the default "memory model" only allows access to 2GB of RAM. Look for a flag that lets you change the memory model to something like "medium" (for pgf compilers I once used -mc_mode=medium, if I remember correctly).
>
> Martin
>
> On Apr 15, 2010, at 5:00 PM, Holly Dail wrote:
>
>> Hello all -
>>
>> I'm trying to build an adjoint code for the Nehalem nodes on Pleiades, and am getting the same error reported in January by Santha here:
>> http://mitgcm.org/pipermail/mitgcm-support/2010-January/006434.html
>>
>> Reducing my nchklev_1 does allow a successful compile, but I don't seem to be able to generate a binary that uses anywhere close to the 3 GB available on the Nehalem nodes.  In my config, if I use nchklev_1 = 30 I get a binary that uses nearly 1 GB, but if I set nchklev_1 = 80 the link fails.
>>
>> The head nodes have 4 GB of memory, but perhaps there is a setting somewhere telling the compiler 1 GB is the maximum?  I imagine I could submit the compile to the queue, but is there another solution?
>>
>> I'm using linux_ia64_ifort+mpi_ice_nas with -xSSE4.2.
>>
>> Thanks -
>> Holly
>>
>> _______________________________________________
>> MITgcm-support mailing list
>> MITgcm-support at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-support
>
>
> _______________________________________________
> MITgcm-support mailing list
> MITgcm-support at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-support