How to profile Message Passing Interface (MPI) applications with the Oracle Solaris Studio Performance Tools. Includes examples from the analysis of performance data and a discussion of supported MPI implementations.
MPI_Finalize(3) MPI MPI_Finalize(3)NAME
MPI_Finalize - Terminates MPI execution environment
SYNOPSIS
int MPI_Finalize( void )
NOTES
All processes must call this routine before exiting. The number of processes running after this routine is called is undefined; it is best
not to perform much more than a return rc after calling MPI_Finalize .
THREAD AND SIGNAL SAFETY
The MPI standard requires that MPI_Finalize be called only by the same thread that initialized MPI with either MPI_Init or MPI_Init_thread
.
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.
LOCATION
finalize.c
8/11/2010 MPI_Finalize(3)
