18.2.5. MPI_Abi_set_fortran_booleans

MPI_Abi_set_fortran_booleans — allows the application to inform the implementation of the literal values of the Fortran booleans.

18.2.5.1. SYNTAX

18.2.5.1.1. C Syntax

int MPI_Abi_set_fortran_booleans(int logical_size, void*
    logical_true, void* logical_false)

18.2.5.1.2. Fortran Syntax

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_ABI_SET_FORTRAN_BOOLEANS(LOGICAL_SIZE, LOGICAL_TRUE, LOGICAL_FALSE, IERROR)
    INTEGER LOGICAL_SIZE, IERROR
    LOGICAL LOGICAL_TRUE, LOGICAL_FALSE

18.2.5.1.3. Fortran 2008 Syntax

USE mpi_f08
MPI_Abi_set_fortran_booleans(logical_size, logical_true, logical_false, ierror)
    INTEGER, INTENT(IN) :: logical_size
    LOGICAL, INTENT(IN) :: logical_true, logical_false
    INTEGER, OPTIONAL, INTENT(OUT) :: ierror

18.2.5.2. INPUT PARAMETERS

  • logical_size: the size of Fortran logical in bytes

  • logical_true: the Fortran literal value TRUE

  • logical_false: the Fortran literal value FALSE

18.2.5.3. OUTPUT PARAMETERS

  • ierror: Fortran only: Error status (integer).

18.2.5.4. DESCRIPTION

MPI_Abi_set_fortran_booleans allows the application to inform the implementation of the literal values of the Fortran booleans. Prior to setting this information, the application should check if the logical values are already set using MPI_Abi_get_fortran_booleans.

logical_size is the size in bytes of a Fortran logical and must be a power of two; otherwise MPI_ERR_ARG is returned. This routine may be called at most once; a subsequent call returns MPI_ERR_ABI.

When Open MPI is built with Fortran logical support, the values returned by MPI_Abi_get_fortran_booleans come from Open MPI’s configured Fortran support. User-supplied values from MPI_Abi_set_fortran_booleans are used by MPI_Abi_get_fortran_booleans only when Open MPI is built without Fortran logical support.

18.2.5.5. ERRORS

Almost all MPI routines return an error value; C routines as the return result of the function and Fortran routines in the last argument.

Before the error value is returned, the current MPI error handler associated with the communication object (e.g., communicator, window, file) is called. If no communication object is associated with the MPI call, then the call is considered attached to MPI_COMM_SELF and will call the associated MPI error handler. When MPI_COMM_SELF is not initialized (i.e., before MPI_Init/MPI_Init_thread, after MPI_Finalize, or when using the Sessions Model exclusively) the error raises the initial error handler. The initial error handler can be changed by calling MPI_Comm_set_errhandler on MPI_COMM_SELF when using the World model, or the mpi_initial_errhandler CLI argument to mpiexec or info key to MPI_Comm_spawn/MPI_Comm_spawn_multiple. If no other appropriate error handler has been set, then the MPI_ERRORS_RETURN error handler is called for MPI I/O functions and the MPI_ERRORS_ABORT error handler is called for all other MPI functions.

Open MPI includes three predefined error handlers that can be used:

  • MPI_ERRORS_ARE_FATAL Causes the program to abort all connected MPI processes.

  • MPI_ERRORS_ABORT An error handler that can be invoked on a communicator, window, file, or session. When called on a communicator, it acts as if MPI_Abort was called on that communicator. If called on a window or file, acts as if MPI_Abort was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, aborts only the local process.

  • MPI_ERRORS_RETURN Returns an error code to the application.

MPI applications can also implement their own error handlers by calling:

Note that MPI does not guarantee that an MPI program can continue past an error.

See the MPI man page for a full list of MPI error codes.

See the Error Handling section of the MPI-5.0 standard for more information.

See also