On Wed, Nov 3, 2010 at 19:48, Barry Smith <bsmith at mcs.anl.gov> wrote:
> I would say it was spurious, but users building PETSc won't know it is > spurious and I like clean compiles with no warnings (even if the warnings > are wrong). Okay, then PETSc needs to avoid any cases of single-malloc for a struct and member. Is this thread really the only one? Jed -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/cdce485b/attachment.html>
