#include "mpi.h" int MPI_Buffer_detach( bufferptr, size ) void *bufferptr; int *size;
|buffer||initial buffer address (choice)
|size||buffer size, in bytes (integer)
int size, mysize, idummy; void *ptr, *myptr, *dummy; MPI_Buffer_detach( &ptr, &size ); MPI_Buffer_attach( myptr, mysize ); ... ... library code ... ... MPI_Buffer_detach( &dummy, &idummy ); MPI_Buffer_attach( ptr, size );
This is much like the action of the Unix signal routine and has the samestrengths (it is simple) and weaknesses (it only works for nested usages).
Note that for this approach to work, MPI_Buffer_detach must return MPI_SUCCESSeven when there is no buffer to detach. In that case, it returns a size ofzero. The MPI 1.1 standard for MPI_BUFFER_DETACH contains the text
The statements made in this section describe the behavior of MPI for buffered-mode sends. When no buffer is currently associated, MPI behaves as if a zero-sized buffer is associated with the process.
This could be read as applying only to the various Bsend routines. Thisimplementation takes the position that this applies to MPI_BUFFER_DETACHas well.
All MPI objects (e.g., MPI_Datatype, MPI_Comm) are of type INTEGERin Fortran.
The Fortran binding for this routine is different. Because Fortrandoes not have pointers, it is impossible to provide a way to use theoutput of this routine to exchange buffers. In this case, only thesize field is set.