[petsc-dev] threadcomm memory leak

[Jed Brown]

On Mon, Jul 16, 2012 at 5:32 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

> Why shouldn't they be the same?  Everything should still work fine. Where
> in PETSc do we make the assumption MPI_COMM_SELF is not MPI_COMM_WORLD and
> why? Except for Shi's new stuff and the new elemental stuff everything else
> in PETSc has worked fine with them being the same for 15 years. Hence the
> problem is likely with Shri's and Hong's interactions with MPI; not with
> the current MPIUNI.


It is a hack to externally reference count based on PETSC_HAVE_MPIUNI or
comparison for equality.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120716/81235ea4/attachment.html>