[MITgcm-devel] Beaufort experiment on mac os x

[Menemenlis, Dimitris (3248)]

Martin, thank you for finding the problematic routine.  I have tried all three:
  NOOPTFILES='gad_c4_adv_x.F gad_u3_adv_x.F'
  NOOPTFILES=''
  NOOPTFILES='ini_masks_etc.F'
on my MacBook Pro, with the darwin_ia32_gfortran build_options file,
and all three work fine and produce the same results.
This is probably because I am using an older version of compiler,
which does not display the -O3 optimization bug in the first place.
So the check-in you suggest below is fine with me.


Torge, could you try replacing
  NOOPTFILES='gad_c4_adv_x.F gad_u3_adv_x.F'
with
  NOOPTFILES='ini_masks_etc.F'
and use -O3 optimization to see if this works on your mac
and if it gets rid of your segmentation fault issue.

Cheers

Dimitris Menemenlis

On Mar 15, 2012, at 2:15 AM, Martin Losch wrote:

> Hi there I compiled with "-g -ftraceback" (and -O3) and used gdb and found that ini_masks_etc.F (line 120) is  the problematic rountine, I don't see why. Anyway, I put this into the list of NOOPTFILES and removed (had to!!!) the -ftree-vectorize option and it works with
>> top
> PID    COMMAND      %CPU  TIME     #TH  #WQ  #POR #MREG RPRVT  RSHRD  RSIZE
> 75875  mitgcmuv     98.7  00:13.07 1/1  0    14   34    98M    240K   101M
> so the approximate 100MB core memory that Dimitris was talking about.
> 
> I can check in this change, but incidentally, do we need the two gad_*.F routines in the NOOPTFILES list? If not, I'll remove them.
> 
> Martin
> 
> 
> On Mar 14, 2012, at 7:37 PM, Torge Martin wrote:
> 
>> Hi Dimitris,
>> 
>> just updated MITgcm and beaufort. I also don't use the -ieee option with genamke2 anymore. 
>> With -O3 I get the segmentation fault, with -O2 it runs just fine.
>> 
>> Torge
>> 
>> On Wed, Mar 14, 2012 at 10:15 AM, Menemenlis, Dimitris (3248) <Dimitris.Menemenlis at jpl.nasa.gov> wrote:
>> Torge, maybe try "-O2".  It will be a bit faster.
>> 
>> Martin, since "-O3" in darwin_amd64_gfortran is problematic,
>> should we downgrade to "-O2" in the CVS repository,
>> until compiler bug is fixed ... or until someone takes the time to
>> locate particular subroutine that causes optimization crash?
>> 
>> Cheers
>> 
>> Dimitris Menemenlis