DragonFly On-Line Manual Pages
    
    
	
MPI_Win_detach(3)                     MPI                    MPI_Win_detach(3)
NAME
       MPI_Win_detach -  Detach memory from a dynamic window
SYNOPSIS
       int MPI_Win_detach(MPI_Win win, const void *base)
       Detaches a previously attached memory region beginning at base. The
       arguments base and win must match the arguments passed to a previous
       call to MPI_Win_attach .
INPUT PARAMETERS
       base   - initial address of memory to be detached
       win    - window object used for communication (handle)
NOTES
       Memory also becomes detached when the associated dynamic memory window
       is freed.
THREAD AND INTERRUPT SAFETY
       This routine is thread-safe.  This means that this routine may be
       safely used by multiple threads without the need for any user-provided
       thread locks.  However, the routine is not interrupt safe.  Typically,
       this is due to the use of memory allocation routines such as malloc or
       other non-MPICH runtime routines that are themselves not interrupt-
       safe.
NOTES FOR FORTRAN
       All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
       an additional argument ierr at the end of the argument list.  ierr is
       an integer and has the same meaning as the return value of the routine
       in C.  In Fortran, MPI routines are subroutines, and are invoked with
       the call statement.
       All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
       Fortran.
ERRORS
       All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error
       value; C routines as the value of the function and Fortran routines in
       the last argument.  Before the value is returned, the current MPI error
       handler is called.  By default, this error handler aborts the MPI job.
       The error handler may be changed with MPI_Comm_set_errhandler (for
       communicators), MPI_File_set_errhandler (for files), and
       MPI_Win_set_errhandler (for RMA windows).  The MPI-1 routine
       MPI_Errhandler_set may be used but its use is deprecated.  The
       predefined error handler MPI_ERRORS_RETURN may be used to cause error
       values to be returned.  Note that MPI does not guarentee that an MPI
       program can continue past an error; however, MPI implementations will
       attempt to continue whenever possible.
       MPI_SUCCESS
              - No error; MPI routine completed successfully.
       MPI_ERR_ARG
              - Invalid argument.  Some argument is invalid and is not
              identified by a specific error class (e.g., MPI_ERR_RANK ).
       MPI_ERR_COUNT
              - Invalid count argument.  Count arguments must be non-negative;
              a count of zero is often valid.
       MPI_ERR_RANK
              - Invalid source or destination rank.  Ranks must be between
              zero and the size of the communicator minus one; ranks in a
              receive ( MPI_Recv , MPI_Irecv , MPI_Sendrecv , etc.) may also
              be MPI_ANY_SOURCE .
       MPI_ERR_TYPE
              - Invalid datatype argument.  Additionally, this error can occur
              if an uncommitted MPI_Datatype (see MPI_Type_commit ) is used in
              a communication call.
       MPI_ERR_WIN
              - Invalid MPI window object
SEE ALSO
       MPI_Win_create_dynamic MPI_Win_attach
                                   11/9/2015                 MPI_Win_detach(3)