[mpich-discuss] [PATCH v2] test: add attrdeleteget, MPI_Attr_get called from delete_fn
Jeff Squyres (jsquyres)
jsquyres at cisco.com
Mon May 20 08:39:19 CDT 2013
On May 18, 2013, at 4:41 PM, Fab Tillier <ftillier at microsoft.com> wrote:
> I agree the standard should clarify (I'll take a look at the ticket you created), and I'd like to see a clarification of the behavior with respect to the attribute delete callbacks. Specifically, the standard does not state explicitly whether the attributes are destroyed within the call to MPI_COMM_FREE, or only once all references on the communicator are released.
Sorry for jumping in late...
I actually brought this exact issue up with the Forum a few years ago. There's a few larger issues:
1. What exactly is allowed to be done in attribute callbacks (or any callbacks, actually) -- to include whether you can GET_ATTR, etc.
2. Is the Fortran attribute extra state parameter passed by value or by reference?
Sadly, it looks like I only made a ticket on #2: https://svn.mpi-forum.org/trac/mpi-forum-web/ticket/159
But for #1, there was some web discussion about this, but the issue never really went anywhere. Here's the first mail about it, from back in 2011:
http://lists.mpi-forum.org/mpi-forum/2011/04/1035.php
--
Jeff Squyres
jsquyres at cisco.com
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
More information about the discuss
mailing list