MPI_WIN_COMPLETE(3)

🎀 NAME 🎀

okay bestie, this is the Open MPI manual page for MPI_Win_complete — yes, the MPI_WIN_COMPLETE(3) one, iykyk. It completes an RMA access epoch on win started by a call to MPI_Win_start. That's the whole name-line vibe: it's the "we are so done with this RMA access epoch" button. 💅

---

✨ SYNTAX ✨

C Syntax

          #include <mpi.h>

          MPI_Win_complete(MPI_Win win)

Fortran Syntax

          USE MPI
          ! or the older form: INCLUDE 'mpif.h'
          MPI_WIN_COMPLETE(WIN, IERROR)

Fortran 2008 Syntax

          USE mpi_f08
          MPI_Win_complete(win, ierror)
               TYPE(MPI_Win), INTENT(IN) :: win
               INTEGER, OPTIONAL, INTENT(OUT) :: ierror

---

💖 INPUT PARAMETERS 💖

• win — Window object (handle). That's your window bestie, the handle you're completing the epoch on.

---

🌸 OUTPUT PARAMETERS 🌸

• ierror — Fortran only: Error status (integer). Fortran girlies get the error status here; C routines get their return value instead.

---

🦋 DESCRIPTION 🦋

MPI_Win_complete is a one-sided MPI communication synchronization call, completing an RMA access epoch on win started by a call to MPI_Win_start.

MPI_Win_complete enforces the completion of preceding RMA calls at the origin and not at the target. A put or accumulate call may not have completed at the target when it has completed at the origin. So basically: origin says "done," but the target may still be catching up — no cap. 😭

---

💅 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. dramatic, but iconic 💀
• 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:

• 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. fr fr, that's important. 🫶

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_Win_start — the call that starts the RMA access epoch this one completes. the other half of the era, bestie ✨

---

👑 COPYRIGHT 👑

2003-2026, The Open MPI Community

mwah 💋 — this page is from Open MPI, dated Sep 11, 2026. now go complete that epoch and slay the RMA game, bestie! 🫶🌈