[mpich-discuss] Compiler optimization flags in MPICH 3.0 rc1

Pavan Balaji balaji at mcs.anl.gov
Fri Nov 16 11:56:34 CST 2012

On 11/16/2012 11:52 AM US Central Time, Yauheni Zelenko wrote:
> But why warnings flags are mixed with optimization ones? I think
> these options should be independent.

They are, unfortunately, not independent.  Some compilers throw some
errors only when the optimization flag is specified.  That's the reason
why we have both options --enable-strict and --enable-strict=noopt.

 -- Pavan

Pavan Balaji

More information about the discuss mailing list