SHMEM_INT_G(3)

💖 NAME 💖

okay bestie, so this is Open MPI's SHMEM_INT_G(3) page, and it's the whole girl-gang of _g functions: shmem_char_g, shmem_float_g, shmem_int_g, shmem_long_g, shmem_short_g, shmem_longlong_g, and shmem_longdouble_g 🎀

What do they do? They're the routines that give you a low latency mechanism to read basic types — that's char, short, int, float, double, long, long long, and long double — from symmetric data objects sitting on remote PEs. It's giving "reach across the network and grab one little value, no drama" ✨

---

🌸 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. One element. One type. One vibe check. 💅

The arguments are as follows:

• addr — the remotely accessible array element or scalar data object which will receive the data on the remote PE. yes bestie, "receive" — that's literally what the page says, don't come for me 🙈
• pe — the number of the remote PE. that's the cutie you're reading from 🫶

⭐ See also: ⭐

intro_shmem(3) shmem_get(3)

---

👑 Copyright 👑

2003-2026, The Open MPI Community

---

that's the whole page, no cap — thanks for reading my little manual moment, mwah 💖 This has been the Open MPI girlies of SHMEM_INT_G(3), dated Sep 10, 2026, copyright 2003-2026, The Open MPI Community. periodt. 🎀✨