MPI_WIN_GET_GROUP(3)

💖 NAME (manual page MPI_WIN_GET_GROUP(3) from Open MPI) 💖

okay bestie, welcome to the Open MPI page for MPI_Win_get_group — yes, the manual name is literally right there in the heading, we’re folding it in, no boring header-line copy-paste here. 🫶

MPI_Win_get_group — Returns a duplicate of the group of the communicator used to create the window.

---

✨ SYNTAX ✨

💅 C Syntax

#include <mpi.h>

MPI_Win_get_group(MPI_Win win, MPI_Group *group)

🎀 Fortran Syntax

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

🦋 Fortran 2008 Syntax

USE mpi_f08
MPI_Win_get_group(win, group, ierror)
     TYPE(MPI_Win), INTENT(IN) :: win
     TYPE(MPI_Group), INTENT(OUT) :: group
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

---

🌸 INPUT PARAMETER 🌸

• win — Window object (handle). 💅

---

🎀 OUTPUT PARAMETERS 🎀

• group — Group of processes that share access to the window (handle). 🫶
• ierror — Fortran only: Error status (integer).

---

🌈 DESCRIPTION 🌈

MPI_Win_get_group returns a duplicate of the group of the communicator used to create the window associated with win. The group is returned in group.

it’s giving “duplicate group, but make it a handle” energy, and honestly? iconic. ✨

---

🚨 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:

• 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.

---

👑 COPYRIGHT 👑

2003-2026, The Open MPI Community

---

that’s the tea, bestie — this MPI_WIN_GET_GROUP(3) page is from Open MPI and stamped Sep 11, 2026. mwah 💋✨