BEMTOH32(9)

okay bestie, welcome to BEMTOH32(9) from the Kernel Developer's Manual — the byte-swapping memory load and store operations page, and yes we're making it cute. 💖

💖 NAME 💖

Meet the whole squad: bemtoh16, bemtoh32, bemtoh64, lemtoh16, lemtoh32, lemtoh64, htobem16, htobem32, htobem64, htolem16, htolem32, htolem64 — all here for byte swapping memory load and store operations. periodt. 💅

✨ SYNOPSIS ✨

#include <sys/types.h>

uint16_t
bemtoh16(volatile const uint16_t *m);

uint32_t
bemtoh32(volatile const uint32_t *m);

uint64_t
bemtoh64(volatile const uint64_t *m);

uint16_t
lemtoh16(volatile const uint16_t *m);

uint32_t
lemtoh32(volatile const uint32_t *m);

uint64_t
lemtoh64(volatile const uint64_t *m);

void
htobem16(volatile uint16_t *m, uint16_t v);

void
htobem32(volatile uint32_t *m, uint32_t v);

void
htobem64(volatile uint64_t *m, uint64_t v);

void
htolem16(volatile uint16_t *m, uint16_t v);

void
htolem32(volatile uint32_t *m, uint32_t v);

void
htolem64(volatile uint64_t *m, uint64_t v);

🌸 DESCRIPTION 🌸

So this API is giving main character energy because it lets you take advantage of an architecture's ability to load and store words in memory of different endians. 🦋 If an architecture has no specialised support for these operations, they will be implemented as a wrapper around the htobe64(3) API. no cap.

These operations are subject to the same alignment restrictions as the host's normal memory loads and stores. like, the alignment rules are not a vibe you can ignore, bestie. 😭

• bemtoh16(), bemtoh32(), bemtoh64() — read a big endian value from the memory located at m into the host's native byte order. 💖
• lemtoh16(), lemtoh32(), lemtoh64() — read a little endian value from the memory located at m into the host's native byte order. ✨
• htobem16(), htobem32(), htobem64() — store the host's native byte ordered value of v as a big endian value in the memory located at m. 🎀
• htolem16(), htolem32(), htolem64() — store the host's native byte ordered value of v as a little endian value in the memory located at m. 🧚

🦋 CONTEXT 🦋

bemtoh16(), bemtoh32(), bemtoh64(), lemtoh16(), lemtoh32(), lemtoh64(), htobem16(), htobem32(), htobem64(), htolem16(), htolem32(), and htolem64() can be called during autoconf, from process context, or from interrupt context. they're flexible like that. 💅

🎀 RETURN VALUES 🎀

bemtoh16(), bemtoh32(), bemtoh64(), lemtoh16(), lemtoh32(), and lemtoh64() return the host's native byte ordered value of the memory at m after the appropriate byteswapping has occurred. 🫶

htobem16(), htobem32(), htobem64(), htolem16(), htolem32(), and htolem64() do not return a value. they're void, they said no return value and they meant it. 💀

🔥 SEE ALSO 🔥

htobe64(3) — go read that one too, iykyk. 👑

⭐ HISTORY ⭐

These functions first appeared in OpenBSD 5.6. iconic behavior, honestly. 🌈

---

💖 cute little sign-off: this page comes from Debian, dated March 31, 2022 — bye bestie, go byteswap responsibly. 🍓✨