<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jul 16, 2012, at 9:46 AM, Jed Brown wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Mon, Jul 16, 2012 at 9:44 AM, Shri <span dir="ltr"><<a href="mailto:abhyshr@mcs.anl.gov" target="_blank">abhyshr@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div id=":7ea"> You need to do similar for your elemental grid to avoid memory leaks when using mpiuni.<br>
<a href="http://petsc.cs.iit.edu/petsc/petsc-dev/rev/169c19e9ea54" target="_blank">http://petsc.cs.iit.edu/petsc/petsc-dev/rev/169c19e9ea54</a></div></blockquote></div><br><div>Isn't the right solution to fix MPIUNI so that they aren't literally the same comm?</div>
</blockquote><br></div><div>Yes, i think so too. If no one objects then i can do that. </div><div>Btw, MPI_COMM_SELF and MPI_COMM_WORLD are same in mpiuni/mpi.h</div><div><div>#define MPI_COMM_WORLD 1</div><div>#define MPI_COMM_SELF MPI_COMM_WORLD</div></div><div><br></div><div> while the fortran version declares these communicators as different. mpiuni/mpif.h</div><div><div> integer MPI_COMM_WORLD</div><div> parameter (MPI_COMM_WORLD = 1)</div><div> integer MPI_COMM_SELF</div><div> parameter (MPI_COMM_SELF = 2)</div></div><br></body></html>