CK_PR_FENCE_RELEASE(3)

✨ CK_PR_FENCE_RELEASE ✨

okay bestie, welcome to the ck_pr_fence_release page from the Concurrency Kit man pages πŸ’– this one's a lil baby function but she is IMPORTANT, i promise.


πŸŽ€ NAME πŸŽ€

ck_pr_fence_release β€” enforce release semantics πŸ¦‹

like. that's the whole name. that's the whole job. slay.


πŸ“š LIBRARY πŸ“š

Concurrency Kit, aka libck β€” you link it with -lck 🫢


🌸 SYNOPSIS 🌸

#include <ck_pr.h>

void
ck_pr_fence_release(void);

no args, no drama, just vibes πŸ’…


πŸ’œ DESCRIPTION πŸ’œ

okay so here's the tea, bestie β˜• ck_pr_fence_release enforces the partial ordering of two specific things:

  • any loads that happen prior to invocation of this function, with respect to any stores that come after it
  • any stores that happen prior to invocation, with respect to any stores that come after it

that's it. that's the whole function. no cap. it's giving "i just do one thing and i do it flawlessly" πŸ‘‘


⭐ RETURN VALUES ⭐

she returns nothing. void. no return value at all. she's not here to give you answers, she's here to give you ordering πŸ˜­πŸ’–


🌈 SEE ALSO 🌈

the whole girlies, all together, one big friend group 🫢:

and if you want even more lore, there's additional information available at http://concurrencykit.org/ ✨


πŸ’€ quick reminder bestie: fencing is not a game, this is real memory-ordering behaviour, use it with intention okay?? i love you.

and that's the whole page!! πŸ’– this one was dated January 2, 2014, and she lives in the CK_PR_FENCE_RELEASE(3) section of the Concurrency Kit manual, so you can always find her again by name πŸŽ€ bye babes, go order some memory correctly πŸ’…βœ¨

πŸ“¦ where this page comes from