[petsc-dev] OpenMP compiler options

2012-05-29 Thread Jed Brown
The OpenMP flags do not definitively identify that OpenMP is used. In particular, IBM XL interprets Cray's option -h omp as being equivalent to -soname omp, then silently ignores the Open MP pragmas. We can perhaps fix this instance by moving -qsmp up in the list, but we may eventually need to

[petsc-dev] OpenMP compiler options

2012-05-29 Thread Matthew Knepley
On Tue, May 29, 2012 at 3:52 PM, Jed Brown jedbrown at mcs.anl.gov wrote: The OpenMP flags do not definitively identify that OpenMP is used. In particular, IBM XL interprets Cray's option -h omp as being equivalent to -soname omp, then silently ignores the Open MP pragmas. We can perhaps fix

[petsc-dev] OpenMP compiler options

2012-05-29 Thread Satish Balay
Perhaps the 'empty' flag check should be at the begining of the list.. [we do have other places in configure where we fix the order in which flags are checked - due to similar conflicts between compilers] Satish On Tue, 29 May 2012, Jed Brown wrote: The OpenMP flags do not definitively

[petsc-dev] OpenMP compiler options

2012-05-29 Thread Jed Brown
On Tue, May 29, 2012 at 10:56 AM, Satish Balay balay at mcs.anl.gov wrote: Perhaps the 'empty' flag check should be at the begining of the list.. No, because most compilers ignore the pragmas when no options are given. I do not know of any portable way, short of running code, to determine