MPI_COMM_IDUP(3)

✨ MPI_COMM_IDUP(3) ✨

okay so this is the Open MPI manual page for MPI_Comm_idup, and bestie, it's literally about starting a nonblocking duplication of an existing communicator with all its cached information. yes, you read that right. nonblocking. duplication. 💅

---

🌸 NAME 🌸

MPI_Comm_idup — start the nonblocking duplication of an existing communicator with all its cached information.

---

🎀 SYNTAX 🎀

C Syntax

#include <mpi.h>

int MPI_Comm_idup(MPI_Comm comm, MPI_Comm *newcomm, MPI_Request *request)

Fortran Syntax

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_COMM_IDUP(COMM, NEWCOMM, REQUEST, IERROR)
     INTEGER COMM, NEWCOMM, REQUEST, IERROR

Fortran 2008 Syntax

USE mpi_f08
MPI_Comm_idup(comm, newcomm, request, ierror)
     TYPE(MPI_Comm), INTENT(IN) :: comm
     TYPE(MPI_Comm), INTENT(OUT) :: newcomm
     TYPE(MPI_Request), INTENT(OUT) :: request
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

---

🦋 INPUT PARAMETER 🦋

• comm — the communicator, aka the handle you're duplicating. it's giving origin story. 💖

---

⭐ OUTPUT PARAMETERS ⭐

• newcomm — a copy of comm (handle). fresh out the oven, same vibe.
• request — the communication request (handle). this is your "lemme know when it's done" ticket. 🎟️
• ierror — Fortran only: error status (integer).

---

💜 DESCRIPTION 💜

so MPI_Comm_idup starts the nonblocking duplication of an existing communicator comm with associated key values. for each key value, the respective copy callback function determines the attribute value associated with this key in the new communicator. and here's the plot twist — one particular action that a copy callback may take is to delete the attribute from the new communicator. dramatic, but valid. 💀

it returns in newcomm a new communicator with the same group, any copied cached information, but a new context (see the “Functionality” subsection of the “Caching” section in the “Groups, Contexts, and Communicators” chapter in the MPI Standard). and heads up: the communicator returned in newcomm will not be available until the request is complete. no peeking early, bestie. 🙈

the completion of a communicator duplication request can be determined by calling any of MPI_Wait, MPI_Waitany, MPI_Test, or MPI_Testany with the request returned by this function. pick your fighter. 🥊

---

🌈 NOTES 🌈

this operation is used to provide a parallel library call with a duplicate communication space that has the same properties as the original communicator. this includes any attributes (see below) and topologies (see the “Process Topologies” chapter in the MPI Standard). 🫶

this call is valid even if there are pending point-to-point communications involving the communicator comm. iconic behavior honestly. a typical call might involve an MPI_Comm_idup at the beginning of the parallel call, and an MPI_Comm_free of that duplicated communicator at the end of the call. other models of communicator management are also possible — you do you. ✨

this call applies to both intra- and intercommunicators.

⚠️ note that it is not defined by the MPI standard what happens if the attribute copy callback invokes other MPI functions. in Open MPI, it is not valid for attribute copy callbacks (or any of their children) to add or delete attributes on the same object on which the attribute copy callback is being invoked. so like... don't. fr fr. 😭

---

💀 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. yeah. everybody. 😵
• 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. very "this is between me and me" of it.
• MPI_ERRORS_RETURN — returns an error code to the application. the polite one. 🎀

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. so like, plan accordingly bestie.

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_Comm_dup
• MPI_Comm_dup_with_info

(go read those too, iykyk 👑)

---

👑 COPYRIGHT 👑

2003-2026, The Open MPI Community

---

and that's the whole page, bestie — mwah 💋 this little gem dropped on Sep 11, 2026 and it's filed under MPI_COMM_IDUP(3) out of Open MPI, straight from The Open MPI Community themselves. slay, go duplicate something. 💖✨🎀