[petsc-dev] threadcomm memory leak

Blaise Bourdin bourdin at lsu.edu
Mon Jul 16 10:13:13 CDT 2012


On Jul 16, 2012, at 10:11 AM, Jed Brown wrote:

> On Mon, Jul 16, 2012 at 10:09 AM, Shri <abhyshr at mcs.anl.gov> wrote:
> Yes, i think so too. If no one objects then i can do that. 
> Btw, MPI_COMM_SELF and MPI_COMM_WORLD are same in mpiuni/mpi.h
> #define MPI_COMM_WORLD       1
> #define MPI_COMM_SELF        MPI_COMM_WORLD
> 
>  while the fortran version declares these communicators as different. mpiuni/mpif.h
>  integer MPI_COMM_WORLD
>        parameter (MPI_COMM_WORLD = 1)
>        integer MPI_COMM_SELF
>        parameter (MPI_COMM_SELF = 2)
> 
> WAT? The Fortran version did something right?

That's because it is tested by people who do stuff with it ;)

Blaise


-- 
Department of Mathematics and Center for Computation & Technology
Louisiana State University, Baton Rouge, LA 70803, USA
Tel. +1 (225) 578 1612, Fax  +1 (225) 578 4276 http://www.math.lsu.edu/~bourdin







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120716/6c94c4cb/attachment.html>


More information about the petsc-dev mailing list