[MITgcm-devel] Beaufort experiment on mac os x

[Art Lazanoff]

Hi Dimitris et al,

I'll do a test run later this morning. Sometimes a second or third
compiler will react to something that the other compilers don't. 

Also, have you tried compiling with -g and running using gdb (or some
other debugger)? You will likely get some more insight into the failure.

Art
-----Original Message-----
From: Menemenlis, Dimitris (3248) <Dimitris.Menemenlis at jpl.nasa.gov>
To: MITgcm-devel at mitgcm.org <MITgcm-devel at mitgcm.org>
Cc: Torge Martin <torge.martin at gmail.com>, Lazanoff, Arthur S.
(ARC-TN)[Computer Sciences Corporation] <arthur.s.lazanoff at nasa.gov>
Subject: Re: [MITgcm-devel] Beaufort experiment on mac os x
Date: Wed, 14 Mar 2012 12:15:56 -0500

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

On Mar 14, 2012, at 10:08 AM, Torge Martin wrote:

> Hi Dimitris, Martin,
> 
> looks like Martin is right. I just found that using the -ieee option
> with genmake2 sets FOPTIM=-O0. This helps to get pass the Segmentation
> Fault.
> 
> Now, I the Beaufort set up is running with this option on my MacPro,
> OS X 10.5.8 (Snow Leopard), 2 x 3 GHz Dual-Core, 4 GB Memory, using
> gcc version 4.0.1 (Apple Inc. build 5465) and
> MITgcm/tools/build_options/darwin_ia32_gfortran.
> 
> Torge
> 
> P.S. Haven't tried running with MPI using both processors, yet.