Re: [mpich-discuss] [PATCH v2] test: add attrdeleteget, MPI_Attr_get called from delete_fn
Pavan Balaji <[email protected]> writes:
Can you point me to the appropriate location in the standard for this? All I can find is:
"The comm_delete_attr_fn function is invoked when a communicator is deleted by MPI_COMM_FREE or when a call is made explicitly to MPI_COMM_DELETE_ATTR."
I don't think it explicitly says that the first argument to delete_fn is valid, but the standard doesn't make a habit of reiterating when arguments are valid. What would be the purpose of passing a comm argument that is going to be (sometimes?) invalid? If you think it *should* be acceptable for an MPI implementation to pass an invalid comm to delete_fn, such that compliant user code *must* ignore that argument, then perhaps we should move the discussion to mpi-forum and clarify the wording in the standard.
participants (1)
-
Jed Brown