[MITgcm-devel] fixing REAL4_IS_SLOW

[Martin Losch]

Hi Jean-Michel,

checked in, yes CPP_EEOPTIONS.h was no different, just for the test  
summary that I sent in the last email I undefined REAL4_IS_SLOW and  
changed it back afterwards.

verification: solid-body and inverted_barometer are good choices; the  
inverted_barometer is such a superfluous experiment, just testing the  
ATMOSPHERIC_LOADING flag, that is long used in other experiments as  
well. With this REAL4_IS_SLOW flag it will have some meaning. On the  
other hand it just tests the basic gfd, maybe add some diagnostics  
(and mnc of course)?

I was also thinking of having a dedicated test where everything is  
tested like this:
 >> cvs co MITgcm
 >> run ./script_that_modifies eesupp/inc/CPP_EEMACROS.h (to set  
#undef REAL4_IS_SLOW, or maybe that can be overriden with a - 
UREAL4_IS_SLOW in a build_options file, I haven't tried that yet?)
 >> run ./testreport
just to see if compilation and execution of code work, because that  
was definitely broken; this test will not, of course, test the  
accuracy. What do you think?

Martin

On 27 Oct 2008, at 02:13, Jean-Michel Campin wrote:

>
> Martin,
>
> looked at those 2 files:
>  CPP_EEMACROS.h and CPP_EEOPTIONS.h
> from your faulks/scratch */eesupp/inc dir
> and you should check-in CPP_EEMACROS.h
> (CPP_EEOPTIONS.h has not changed, right ?)
>
> And I started to test this on:
>   solid-body.cs-32x32x1
> + inverted_barometer (Not yet added mnc)
> with g77, gfortran & ifort (on my laptop) and seems to work.
> get all 16 identical digits between the 3 compilers, for both exp.
> I also tried natl_box (with mnc), it runs with g77 but I am getting
> floating exception / floating invalid with gfortran / ifort
> (wscale_ in kpp_routines.f).
>
> I can try pgf once we've decided which one to switch to _rs=real*4
>
> Cheers,
> Jean-Michel
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel