CK_PR_STORE(3)

💾 ck_pr_store(3) — atomic volatile store operations 💾

okay bestie sit DOWN because we're talking about ck_pr_store(3) from the Concurrency Kit and honestly? she's giving quiet luxury. no drama, no return value, just vibes and perfect memory ordering. 🎀

📚 LIBRARY 📚

Concurrency Kit — you link her with -lck and then she's yours. 💅

✨ SYNOPSIS ✨

first things first, you gotta summon the header:

#include <ck_pr.h>

and then, pick your fighter. nine of them. all iconic, all tiny:

void
ck_pr_store_ptr(void *target, void *value);

void
ck_pr_store_double(double *target, double value);

void
ck_pr_store_uint(unsigned int *target, unsigned int value);

void
ck_pr_store_int(int *target, int value);

void
ck_pr_store_char(char *target, char value);

void
ck_pr_store_64(uint64_t *target, uint64_t value);

void
ck_pr_store_32(uint32_t *target, uint32_t value);

void
ck_pr_store_16(uint16_t *target, uint16_t value);

void
ck_pr_store_8(uint8_t *target, uint8_t value);

one for every size of your little heart's content 🫶

🦋 DESCRIPTION 🦋

so here's the tea, and it's actually really good tea:

the whole ck_pr_store(3) family does exactly one thing — it atomically stores the value you pass in as value into the memory location that target points at. that's it. that's the whole job. she doesn't overcomplicate, she doesn't do side quests, she just puts the thing where you asked her to put the thing. 💖

and the way that she ALWAYS serves as an implicit compiler barrier?? no cap. the compiler is not gonna reorder her, she's not susceptible to compiler re-ordering, periodt. your writes stay exactly where you wrote them. main character energy in the memory model. 🔥

ngl this is the one you reach for when you need a write that the compiler respects and the hardware won't shuffle behind your back. she's the reliable bestie. 🌸

👑 RETURN VALUES 👑

the way that she returns... nothing. 💀

fr fr, this family of functions has no return value. she does the thing and she leaves. no receipt, no follow-up text, no notes. just a clean store and a goodbye. 🧚

🌈 SEE ALSO 🌈

your recommended reading list, bestie — go stan all of them:

• ck_pr_fence_load(3)
• ck_pr_fence_load_depends(3)
• ck_pr_fence_store(3)
• ck_pr_fence_memory(3)
• ck_pr_add(3)
• ck_pr_load(3)
• ck_pr_fas(3)
• ck_pr_faa(3)
• ck_pr_inc(3)
• ck_pr_dec(3)
• ck_pr_neg(3)
• ck_pr_not(3)
• ck_pr_sub(3)
• ck_pr_and(3)
• ck_pr_or(3)
• ck_pr_xor(3)
• ck_pr_cas(3)
• ck_pr_btc(3)
• ck_pr_bts(3)
• ck_pr_btr(3)

and if you want even more lore, the extra info lives at http://concurrencykit.org/ 🌐

okay that's the whole page!! go write some atomic stores and be amazing 💜

🌸 this little beauty dropped on April 15, 2013, and she's part of the Concurrency Kit — it's ck_pr_store(3), and yes, she slayed. 🎀✨