SHMEM_LONG_SET(3)

💖 SHMEM_LONG_SET(3) 💖

okay bestie, gather round, because today we're talking about the set girlies of Open MPI ✨ This page covers shmem_double_set, shmem_float_set, shmem_int_set, shmem_long_set, shmem_longlong_set, shmem_int4_set, shmem_int8_set, shmem_real4_set, shmem_real8_set — and what they all do is atomically set the value of a remote data object. that's the whole vibe. 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 the set routines write the value into the address target on pe, and they do it as an atomic operation. 💅 single move, no in-between states, immaculate behavior. periodt.

the arguments are giving:

• target — the remotely accessible data object to be set on the remote PE 🫶 (this is the thing getting a glow-up from across the network)
• value — the value to be atomically written to the remote PE ⭐ (the new fit, the new look)
• pe — an integer that indicates the PE number upon which target is to be updated. if you're using Fortran, it must be a default integer value 🌈 (yes, default. don't get cute with it.)

---

💜 RETURN VALUES 💜

NONE

...that's it. that's the return value. she returns nothing because she already ate on the remote side. iconic behavior honestly. 🔥

also see: intro_shmem(3) — go read it, bestie, it's the lore 🦋

---

👑 Copyright

2003-2026, The Open MPI Community

---

and that's the whole page, bestie!! Open MPI SHMEM_LONG_SET(3), dated Sep 10, 2026 — you literally know remote atomic sets now. go forth and slay. mwah 💖✨🎀