MPI_INFO_DUP(3)

πŸ’– MPI_INFO_DUP(3) β€” Open MPI, bestie edition πŸ’–

okay so like. this is MPI_INFO_DUP(3) from the Open MPI manual, and it's genuinely one of the easiest ones to love. it duplicates an info object. that's it. that's the whole vibe. πŸŽ€


✨ NAME ✨

MPI_Info_dup β€” duplicates an info object. literally copy-paste but ✨official✨


✨ SYNTAX ✨

C Syntax

#include <mpi.h>

int MPI_Info_dup(MPI_Info info, MPI_Info *newinfo)

Fortran Syntax

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_INFO_DUP(INFO, NEWINFO, IERROR)
     INTEGER         INFO, NEWINFO, IERROR

Fortran 2008 Syntax

USE mpi_f08
MPI_Info_dup(info, newinfo, ierror)
     TYPE(MPI_Info), INTENT(IN) :: info
     TYPE(MPI_Info), INTENT(OUT) :: newinfo
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

🌸 INPUT PARAMETER 🌸

  • info β€” the info object (handle). the one you're cloning, the blueprint, the moment. πŸ‘‘

πŸ¦‹ OUTPUT PARAMETERS πŸ¦‹

  • newinfo β€” the info object (handle). the fresh new baby, the copy, the main character. ✨
  • ierror β€” Fortran only: error status (integer).

πŸ’… DESCRIPTION πŸ’…

MPI_Info_dup duplicates an existing info object, creating a new object, with the same (key,value) pairs and the same ordering of keys.

like. same pairs, same order, an identical twin. not me being obsessed with key ordering being preserved fr fr 😭 the way that it just keeps everything in line? iconic. periodt. πŸ’–


πŸ’€ 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.

heads up bestie: when MPI errors show up, the error handling situation is real and the flow above is exactly how Open MPI routes it. no guesses, no improvising. πŸ’…

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

  • MPI_ERRORS_ARE_FATAL β€” Causes the program to abort all connected MPI processes. (yeah. all of them. πŸ’€)
  • 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. the polite one. the one that hands you the receipt instead of setting the building on fire. 🧚

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

  • MPI_Comm_create_errhandler then MPI_Comm_set_errhandler
  • MPI_File_create_errhandler then MPI_File_set_errhandler
  • MPI_Session_create_errhandler then MPI_Session_set_errhandler or at MPI_Session_init
  • MPI_Win_create_errhandler then MPI_Win_set_errhandler

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-3.1 standard for more information.

See also:

  • MPI_Info_create
  • MPI_Info_delete
  • MPI_Info_free
  • MPI_Info_get
  • MPI_Info_set

2003-2026, The Open MPI Community


and that's the whole page bestie!! 🫢 this came out of Open MPI, dated Sep 10, 2026, and the copyright belongs to 2003-2026, The Open MPI Community. go forth and duplicate ur info objects, u absolute icon. πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from