SHMEM_LONGLONG_G(3)

💅 SHMEM_LONGLONG_G(3) — the Open MPI glow-up ✨

okay so bestie, you're reading a page from the Open MPI manual, and honestly? this one's a little family reunion. it's the whole squad of "get a single value off a friend's memory" routines, and the page is filed under shmem_longlong_g because someone had to be the main character 💫

---

✨ NAME ✨

shmem_char_g(3), shmem_float_g(3), shmem_int_g(3), shmem_long_g(3), shmem_short_g(3), shmem_longlong_g(3), shmem_longdouble_g(3) — these routines provide a low latency mechanism to read basic types (char, short, int, float, double, long, long long, long double) from symmetric data objects on remote PEs. like, you reach across the cluster and grab one little value. lowkey iconic 🫶

---

🌸 SYNOPSIS 🌸

C or C++:

#include <mpp/shmem.h>

char shmem_char_g(const char *addr, int pe)

short shmem_short_g(const short *addr, int pe)

int shmem_int_g(const int *addr, int pe)

long shmem_long_g(const long *addr, int pe)

long shmem_longlong_g(const long long *addr, int pe)

float shmem_float_g(const float *addr, int pe)

double shmem_double_g(const double *addr, int pe)

long shmem_longdouble_g(const long double *addr, int pe)

not me listing all eight of them and every single signature staying exactly the same 😭💖

---

🦋 DESCRIPTION 🦋

these routines provide a very low latency get capability for single elements of most basic types.

fr fr, that's the whole vibe: one element, one type, one trip. no cap.

the arguments are as follows:

• addr — the remotely accessible array element or scalar data object which will receive the data on the remote PE. 👈 literally the destination, bestie
• pe — the number of the remote PE. like the friend's ID in the group chat 💅

---

🎀 SEE ALSO: 🎀

• intro_shmem(3)
• shmem_get(3)

go read those next, iykyk 🌈

---

👑 COPYRIGHT 👑

2003-2026, The Open MPI Community

---

and that's the whole page, periodt 💀✨ official source: Open MPI, dated May 14, 2026 — love that for us. now go get your single element, bestie, and slay 🦋💜