MPI_Comm_set_name - Sets the print name for a communicator
int MPI_Comm_set_name(MPI_Comm comm, const char *comm_name)
- - communicator to name (handle)
- - Name for communicator
This routine is thread and interrupt safe only if no MPI routine that updates or
frees the same MPI object may be called concurrently with this routine.
The MPI standard defined a thread-safe interface but this does not mean that all
routines may be called without any thread locks. For example, two threads must
not attempt to change the contents of the same MPI_Info
concurrently. The user is responsible in this case for using some mechanism,
such as thread locks, to ensure that only one thread at a time makes use of
All MPI routines in Fortran (except for MPI_WTIME
have an additional argument ierr
at the end of the argument list.
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
All MPI objects (e.g., MPI_Datatype
) are of type
All MPI routines (except MPI_Wtime
) 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 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
guarentee that an MPI program can continue past an error; however,
MPI implementations will attempt to continue whenever possible.
- - No error; MPI routine completed successfully.
- - Invalid communicator. A common error is to use a null communicator in a
call (not even allowed in MPI_Comm_rank ).