[MITgcm-devel] genmake2 and fflags

[Jean-Michel Campin]

Hi Martin,

2 little thing:
1) if one S/R from a package needs to be inlined, this solution
would not work, right ? So, apart from my coupler building,
there is a need to do something more flexible.
2) those FEXTRAFLAGS are only used to link, right ?
If this is the case, I would prefer a different name 
(that reflect the LINK stage).
3) what happen if you add in this "exp" list an object file
(e.g., foo.o) that don't appear in the "expin" .F files ?
4) From constantinos: Is there a way (compiler option) to
do those inlining automaticly ? We know some compiler that
can do that, so but no idea about this one.

I the mean time, I suggest that you check-in the modified optfile
and the changes in genmake2 (commented out ?), so that we
can see exactly what is needed. It does nt look very
easy to make it works in general, because the syntax of 
those inlining instructions are compiler specific, but we
could try something.

Cheers,
Jean-Michel 

On Wed, Sep 26, 2007 at 11:03:26AM +0200, Martin Losch wrote:
> Hi Jean Michel,
> 
> currently I want to use something like this:
> 
> FEXTRAFLAGS='-pi fullmsg  
> exp=timestep_tracer,ilnblnk,ifnblnk,cycle_tracer,pressure_for_eos  
> rexp=bar2,fool_the_compiler  
> expin=timestep_tracer.F,fool_the_compiler.F,bar2.F,utils.F,cycle_tracer. 
> F,pressure_for_eos.F'
> 
> for the sxf90 compiler for our SX8. These are all files that are  
> always used (as far as I can see, either in model/src or eesupp/src).  
> When I add this to FFLAGS in the opt file, all genmake2 fortran-tests  
> fail (no netcdf, etc) because the compiler looks for the the files  
> specified in expin=*.F before they are linked to the directory.
> The FEXTRAFLAGS (or whatever name you prefer) will not be used  
> anywhere and is empty by default, so it should not affect any other  
> experiment (although I did not try). Maybe you want to test this on  
> some of your experiments which you find critical? I am attaching my  
> "new" genmake2 and the corresponding build options file to show an  
> example usage. Tell me what you think.
> 
> Martin
> 



> 
> On 26 Sep 2007, at 04:32, Jean-Michel Campin wrote:
> 
> >Hi Martin,
> >
> >What kind of FFLAGS do you have to specify for this inlining ?
> >
> >I am little bit concern that this will break some building
> >where those S/R are not compiled (pkg not compiled,
> >or our coupler in verification/cpl_aim+ocn/build_cpl
> >with empty STANDARDDIRS, i.e., without model/src nor eesup/src)
> >
> >Jean-Michel
> >
> >On Tue, Sep 25, 2007 at 09:49:03PM +0200, Martin Losch wrote:
> >>Hi there,
> >>
> >>for our SX8 I would like to include a list of routines to inlined in
> >>the build_options file. Unfortunately that does not work with FFLAGS,
> >>because then all the little tests in genmake2 look for the routines/
> >>files to inlined and fail. I have included an extra variable
> >>FEXTRAFLAGS into genmake2 that can contain such compiler options that
> >>should not be used in the genmake2-tests. It is only used to actually
> >>write the makefile: FFLAGS=${FFLAGS} ${FEXTRAFLAGS}. Is this OK to
> >>check in? Or do we already have something like that and I just didn't
> >>find it?
> >>
> >>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
> 

> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel