[MITgcm-devel] testreport again

[Martin Losch]

Such an option would be great, because it would help my tests, but not urgent (going on a 2weeks vacation now). I’ll look into it afterwards (unless you have good idea and time to spent (o;)

Martin

> On 24 Mar 2015, at 15:08, Jean-Michel Campin <jmc at ocean.mit.edu> wrote:
> 
> Hi Martin,
> 
> I would prefer to keep the testreport built as close as possible
> to the "normal" built, so that we really "test" experiments in
> the same conditions.
> The other thing is that I am not sure if this "small_f" target will fix completly
> the inlining issue for AD and OAD built, but it does not matter too much.
> 
> What about adding a new option to testreport that would go through this
> intermediate "samll_f" step ?
> 
> Cheers,
> Jean-Michel
> 
> On Tue, Mar 24, 2015 at 01:22:03PM +0100, Martin Losch wrote:
>> Hi there,
>> 
>> do you think we can modify the build procedure for testreport? I.e. in
>> makemodel()
>> replace 
>> 	    $MAKE_CMD $TARG >> make.tr_log 2>&1
>> by
>> 	    $MAKE_CMD small_f >> make.tr_log 2>&1
>> 	    $MAKE_CMD $TARG >> make.tr_log 2>&1
>> 
>> On my vector computer (we have a new one!), explicit inlining only works if ***all*** “small_f" files are availabe when the compiler is called, and just doing “make” does not work. Can we find a solution for this? Alternatively I have turn off explicit inlining for the tests, which I would like to avoid.
>> 
>> Martin
>> 
>> 
>> _______________________________________________
>> MITgcm-devel mailing list
>> MITgcm-devel at mitgcm.org
>> http://mitgcm.org/mailman/listinfo/mitgcm-devel
> 
> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel