MPI_WIN_DELETE_ATTR(3)

💖 MPI_Win_delete_attr(3)

okay so welcome to the Open MPI manual page for MPI_Win_delete_attr, aka the routine that literally deletes an attribute from a window 💅✨. This is your bestie-approved guide, and yes, every technical detail is still here — no cap.

---

🎀 NAME

MPI_Win_delete_attr — deletes an attribute from a window, bestie. That's the whole vibe. 🫶

---

✨ SYNTAX

🌸 C Syntax

#include <mpi.h>

int MPI_Win_delete_attr(MPI_Win win, int win_keyval)

🦋 Fortran Syntax

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

🧚 Fortran 2008 Syntax

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

---

💅 INPUT/OUTPUT PARAMETER

• win — Window from which the attribute is deleted (handle). This is the window getting its little cleanup moment ✨.

---

💜 INPUT PARAMETER

• win_keyval — Key value (integer). It's the key-value sidekick for the deletion, iykyk.

---

🌈 OUTPUT PARAMETER

• ierror — Fortran only: Error status (integer). The Fortran girlies get the status here 🎀.

---

⭐ NOTES

Note that it is not defined by the MPI standard what happens if the delete_fn callback invokes other MPI functions. In Open MPI, it is not valid for delete_fn callbacks (or any of their children) to add or delete attributes on the same object on which the delete_fn callback is being invoked. So like… don't do that, bestie 😭💀.

---

🔥 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. Very main-character exit, but make it everyone's 😭.
• 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. Lowkey the "here's your receipt" option 🧾.

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. That's not a vibe check you want to fail 💀.

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 whole page, bestie — stay slaying with Open MPI, and remember this one is dated Sep 11, 2026 🎀✨