On Jul 31, 2017, at 3:51 PM, Chuck Atkins
mailto:chuck.atk...@kitware.com>> wrote:
Hi Tim,
If the Cray flags are for wrapper scripts, why do we need specific flags for
that instead of using the underlying compiler flags?
Sort answer: It's the "Cray" way of doing things.
Long answer: The targ
Hi Tim,
> If the Cray flags are for wrapper scripts, why do we need specific flags
> for that instead of using the underlying compiler flags?
>
Sort answer: It's the "Cray" way of doing things.
Long answer: The target-cpu flag sometimes just controlls the -march flags
(or equiv) but it can also
If the Cray flags are for wrapper scripts, why do we need specific flags for
that instead of using the underlying compiler flags?
I’m guessing you intend this for the 17.2 branch as well?
-Tim
> On Jul 31, 2017, at 2:53 PM, Chuck Atkins wrote:
>
> Note that the Cray flags (-target-cpu=) need
Note that the Cray flags (-target-cpu=) need to come first since the
cray programming environment uses wappers around other compilers. By
checking the wrapper flags first, you can be sure to match the wrapper
flag instead of the underlying compiler (gcc, intel, pgi, etc.) flags.
Signed-off-by: Ch
