SHMEM_LONG_G(3)

okay so bestie, welcome to SHMEM_LONG_G(3) 💖 this is an Open MPI manual page, and it’s lowkey iconic. Vibe check: the whole get-routine squad is here, no cap.

✨ NAME ✨

the whole squad is: shmem_char_g(3), shmem_float_g(3), shmem_int_g(3), shmem_long_g(3), shmem_short_g(3), shmem_longlong_g(3), and 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. It’s giving “grab a basic type from a remote PE, but make it fast” energy, and honestly? Obsessed.

---

✨ 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)

---

💅 DESCRIPTION 💅

These routines provide a very low latency get capability for single elements of most basic types. literally the main character energy of this page: one element, basic type, low latency, periodt 💅

The arguments are as follows:

• addr — the remotely accessible array element or scalar data object which will receive the data on the remote PE. That’s the destination bestie 🎀
• pe — the number of the remote PE. iykyk 🌸

okay but fr fr: addr is the remotely accessible array element or scalar data object, and it receives the data on the remote PE. pe is just the remote PE number. iconic, simple, slay.

---

🌈 SEE ALSO 🌈

• intro_shmem(3)
• shmem_get(3)

go read those too, bestie 🦋

---

🎀 COPYRIGHT 🎀

2003-2026, The Open MPI Community

✨ that’s the tea from Open MPI — this page is dated May 14, 2026, and SHMEM_LONG_G(3) is signing off 💖💅