[MITgcm-devel] [MITgcm-cvs] MITgcm/tools/build_options CVS Commit
David Ferreira
dfer at mit.edu
Mon Apr 12 09:55:40 EDT 2010
On 4/11/10 10:07 AM, Menemenlis, Dimitris (3248) wrote:
>> My suggestions:
>> a) Separate optfiles (per queue). It explodes the number of optfiles but solves
>> the problem for good.
>> b) The "generic" Pleides optfile uses the -ax instead of the -x flag. That flag
>> builds a generic binary with optional code paths depending on the actual
>> processor used. So I would have a -axSSSE3,SSE4.1 (and in the future ,SSE4.2)
>>
>>
Actually, I don't mind having just one optile file with the lowest
common denominator. I just
thought that we should provide the highest and that users by reading the
NAS doc or
comments in the optfile or talk to someone would learn about the
multiple queues/optimization.
Obviously, it doesn't work (well it does, but at a fairly high price
even for people who use
pleiades everyday).
Let's just change 4.2 to 4.1.
david
More information about the MITgcm-devel
mailing list