SHMEM_FLOAT_SET(3)

💖 SHMEM_FLOAT_SET(3) — bestie edition 💖

okay so this is the Open MPI man page for the whole shmem_*_set girlies — shmem_double_set, shmem_float_set, shmem_int_set, shmem_long_set, shmem_longlong_set, shmem_int4_set, shmem_int8_set, shmem_real4_set, and shmem_real8_set (the actual header name is SHMEM_FLOAT_SET, she's the main character of the file, but they all share 💅).

and what do they do?? they atomically set the value of a remote data object ✨ like, yes, you're reaching over into somebody else's PE and setting a value, and it's atomic so nobody's gonna catch you mid-write, no cap 🫶

---

✨ SYNOPSIS ✨

C or C++:

#include <mpp/shmem.h>

void shmem_double_set(double *target, double value, int pe)

void shmem_float_set(float *target, float value, int pe)

void shmem_int_set(int *target, int value, int pe)

void shmem_long_set(long *target, long value, int pe)

void shmem_longlong_set(long long *target, long long value, int pe)

Fortran:

INCLUDE "mpp/shmem.fh"

INTEGER pe

CALL SHMEM_INT4_SET(target, value, pe)
CALL SHMEM_INT8_SET(target, value, pe)
CALL SHMEM_REAL4_SET(target, value, pe)
CALL SHMEM_REAL8_SET(target, value, pe)

---

🌸 DESCRIPTION 🌸

so basically the set routines write the value into the address target on pe as an atomic operation. that's the whole vibe. one shot, all-or-nothing, no half-written nonsense 💀✨

the arguments are giving:

• target — the remotely accessible data object that's getting set on the remote PE. she's the destination, the moment, the it-girl 🎀
• value — the value being atomically written to the remote PE. the payload. the reason we're all here 🦋
• pe — an integer that says which PE number target is getting updated on. and heads up bestie, if you're in Fortran, it has to be a default integer value — do not come at her with some fancy kind, it's not the move 🙈

---

💀 RETURN VALUES 💀

NONE

like, literally nothing comes back. she gives and does not receive. iconic behavior, honestly 👑

See also: intro_shmem(3)

---

and that's the tea, bestie!! this gorgeous artifact is courtesy of Open MPI, dated Sep 10, 2026, and the copyright situation is 2003-2026, The Open MPI Community — show her some respect, she's been holding it down since 2003 💜 🌈⭐🧚