[petsc-dev] CFLAGS and COPTFLAGS
Jed Brown
jed at jedbrown.org
Sun Jan 19 21:22:31 CST 2014
Barry Smith <bsmith at mcs.anl.gov> writes:
> Yes.*
That leads to sprawling threads like this one.
http://www.open-mpi.org/community/lists/users/2008/10/6891.php
Being stupid might not decrease the incidence of weird behavior, but the
fewer "smart" components in the chain, the easier it is to debug.
> And BTW, you do know my opinion of compiler wrappers!
I have the same opinion.
> Barry
>
> * But note that we have not yet discussed the case where PETSc
> compilers the MPI implementation and what optimization flags we pass
> down there.
MPICHLIB_CFLAGS when building MPICH. IMO, wrappers should never include
optimization flags.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140119/ae05091e/attachment.sig>
More information about the petsc-dev
mailing list