SHMEM_CHAR_PUT(3)

📦
version 5.0.10 · 7 versions
, in ubuntu stonking

💖 SHMEM_CHAR_PUT(3) — the Open MPI one 💖

okay bestie, sit DOWN, because this is the glow-up of shmem_character_put(3). It's a whole family of routines — eighteen of them, one big happy put-put-put squad — and they all do one thing: they hand data to a specific processing element (PE). That's the whole vibe. Transfers data to a specified PE. Periodt.

Here's the full crew, no one left out:

✨ SYNOPSIS ✨

so if you're a C or C++ girly, you're gonna include this header:

#include <mpp/shmem.h>

and then all of these are yours, fr fr:

void shmem_double_put(double *target, const double *source,
  size_t len, int pe)

void shmem_float_put(float *target, const float *source,
  size_t len, int pe)

void shmem_int_put(int *target, const int *source, size_t len,
  int pe)

void shmem_long_put(long *target, const long *source,
  size_t len, int pe)

void shmem_longdouble_put(long double *target,
  const long double *source, size_t len, int pe)

void shmem_longlong_put(long long *target,
  const long long *source, size_t len, int pe)

void shmem_put32(void *target, const void *source, size_t len,
  int pe)

void shmem_put64(void *target, const void *source, size_t len,
  int pe)

void shmem_put128(void *target, const void *source, size_t len,
  int pe)

void shmem_putmem(void *target, const void *source, size_t len,
  int pe)

void shmem_short_put(short *target, const short *source,
  size_t len, int pe)

and for the Fortran besties, it's giving INCLUDE energy:

INCLUDE "mpp/shmem.fh"

INTEGER len, pe

CALL SHMEM_CHARACTER_PUT(target, source, len, pe)

CALL SHMEM_COMPLEX_PUT(target, source, len, pe)

CALL SHMEM_DOUBLE_PUT(target, source, len, pe)

CALL SHMEM_INTEGER_PUT(target, source, len, pe)

CALL SHMEM_LOGICAL_PUT(target, source, len, pe)

CALL SHMEM_PUT(target, source, len, pe)

CALL SHMEM_PUT4(target, source, len, pe)

CALL SHMEM_PUT8(target, source, len, pe)

CALL SHMEM_PUT32(target, source, len, pe)

CALL SHMEM_PUT64(target, source, len, pe)

CALL SHMEM_PUT128(target, source, len, pe)

CALL SHMEM_PUTMEM(target, source, len, pe)

CALL SHMEM_REAL_PUT(target, source, len, pe)

🌸 DESCRIPTION 🌸

okay so here's the tea ☕ — these routines transfer nelems elements of the data object at address source on the calling PE, over to the data object at address target on the remote PE pe.

and here's the important part, don't skip it: these routines start the remote transfer and may return before the data is delivered to the remote PE. it's giving "sent the text, didn't wait for the read receipt" 💀

Also, the delivery of data into the data object on the destination PE from different put calls may occur in any order. Because of this, two successive put operations may deliver data out of order unless you introduce a call to shmem_fence(3) between the two calls. so like… wrap it up, fence it, keep it cute. 🎀

The arguments are as follows:

  • target — the data object to be updated on the remote PE. this one must be remotely accessible, no exceptions bestie.
  • source — the data object holding the data that's getting copied.
  • len — number of elements in the target and source arrays. len must be of type integer. if you're in Fortran, it has to be a constant, variable, or array element of default integer type.
  • pe — the PE number of the remote PE. pe must be of type integer. if you're in Fortran, same deal: a constant, variable, or array element of default integer type.

The target and source data objects must conform to certain typing constraints, which are as follows:

  • shmem_putmem — Fortran: any noncharacter type. C: any data type. len is scaled in bytes.
  • shmem_put4, shmem_put32 — any noncharacter type that has a storage size equal to 32 bits.
  • shmem_put8, shmem_put64 — any noncharacter type that has a storage size equal to 64 bits.
  • shmem_put128 — any noncharacter type that has a storage size equal to 128 bits.
  • shmem_short_put — elements of type short.
  • shmem_int_put — elements of type int.
  • shmem_long_put — elements of type long.
  • shmem_longlong_put — elements of type long long.
  • shmem_float_put — elements of type float.
  • shmem_double_put — elements of type double.
  • shmem_longdouble_put — elements of type long double.
  • SHMEM_CHARACTER_PUT — elements of type character. len is the number of characters to transfer. The actual character lengths of the source and target variables are ignored.
  • SHMEM_COMPLEX_PUT — elements of type complex of default size.
  • SHMEM_DOUBLE_PUT — (Fortran) elements of type double precision.
  • SHMEM_INTEGER_PUT — elements of type integer.
  • SHMEM_LOGICAL_PUT — elements of type logical.
  • SHMEM_REAL_PUT — elements of type real.

and if you're using Fortran, data types must be of default size. for example, a real variable must be declared as REAL, REAL*4, or REAL(KIND=4). no sneaky custom sizes, queen. 💅

🦋 EXAMPLES 🦋

here's a shmem_put moment for the C/C++ girlies:

#include <stdio.h>
#include <mpp/shmem.h>

main()
{
  long source[10] = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 };
  static long target[10];
  shmem_init();

  if (shmem_my_pe() == 0) {
    /* put 10 words into target on PE 1 */
    shmem_long_put(target, source, 10, 1);
  }
  shmem_barrier_all();  /* sync sender and receiver */
  if (shmem_my_pe() == 1)
    shmem_udcflush();  /* not required on Altix systems */
  printf("target[0] on PE %d is %d\n", shmem_my_pe(), target[0]);
}

👑 SEE ALSO 👑

go read these too, iykyk:

Copyright — 2003-2026, The Open MPI Community 💜

and that's the whole page, bestie. this was SHMEM_CHAR_PUT(3) from the Open MPI crew, dated Sep 10, 2026 — go forth and put responsibly (and fence your puts, i'm begging 🫶✨).

📦 where this page comes from