ATOMICAND(3G)

💖 ATOMICAND 💖 (that's section 3G bestie, the GL one)

okay so real talk, this is the manual page for atomicAnd, and it lives in section 3G of the manual. it's giving shader-core, it's giving concurrency, and honestly? it ate. let's get into it. 🦋

---

✨ NAME ✨

atomicAnd — do an atomic logical AND operation to a variable. that's it, that's the whole job. 💅

---

🌸 DECLARATION 🌸

here's the two flavors, copy them exactly bestie, do not freestyle:

int atomicAnd(inout int mem, int data);

uint atomicAnd(inout uint mem, uint data);

two overloads. int version and uint version. iconic of them. 👑

---

🎀 PARAMETERS 🎀

• mem — the variable you're using as the target of the operation. this is the thing getting ANDed, the main character fr.
• data — the data that gets logically ANDed with mem. the sidekick that shows up and changes everything. 💜

---

💫 DESCRIPTION 💫

okay so atomicAnd performs an atomic logical AND of data with the contents of mem… and then — and this is the good part — it returns the original contents of mem from before the logical operation occured. yes, before. the past version. the pre-glow-up value. ✨

and the contents of the memory being updated by the atomic operation are guaranteed not to be modified by any other assignment or atomic memory function in any shader invocation between the time the original value is read and the time the new value is written. so nobody's out here sneaking in and messing with your variable mid-operation. no cap. the lock is locked, the vibe is protected, we love a race-condition-free queen. 🫶

⚠️ now the important part, listen up: atomic memory functions are supported only for a limited set of variables. a shader will fail to compile if the value passed to the mem argument of an atomic memory function does not correspond to a buffer or shared variable. so don't just pass whatever, bestie, the compiler WILL clock you. 💀

but! it IS acceptable to pass an element of an array or a single component of a vector to the mem argument of an atomic memory function, as long as the underlying array or vector is a buffer or shared variable. so array elements and vector components? totally fine, slay. 🍓

---

🌈 VERSION SUPPORT 🌈

here's the vibe check across every OpenGL Shading Language version, function name atomicAnd:

• 1.10 — - nope, not invited 🙈
• 1.20 — - still no 😭
• 1.30 — - nope
• 1.40 — - nope
• 1.50 — - nope
• 3.30 — - nope
• 4.00 — - nope
• 4.10 — - nope
• 4.20 — - nope
• 4.30 — ✔ FINALLY. she arrived. 👑
• 4.40 — ✔ still here, still thriving ✨
• 4.50 — ✔ and still eating 🔥

so like, 4.30 and up only. anything before that is a no from her. periodt.

---

🦋 SEE ALSO 🦋

go give these siblings some love, they're all in the same atomic family:

• atomicAdd()
• atomicOr()
• atomicXor()
• atomicMin()
• atomicMax()
• atomicExchange()
• atomicCompSwap()

---

👑 COPYRIGHT 👑

Copyright © 2011-2014 Khronos Group. This material may be distributed subject to the terms and conditions set forth in the Open Publication License, v 1.0, 8 June 1999. http://opencontent.org/openpub/.

---

👑 COPYRIGHT 👑 (yes, again, they said it twice)

Copyright © 2012-2014 Khronos Group

---

and that's the whole page bestie!! 🎀💖 the source line is literally [FIXME: source] (they left it as a placeholder, we respect the honesty) and this version is dated 01/03/2018. it's the ATOMICAND(3G) page, it's giving Khronos, it's giving atomic, and it's done. iykyk. ✨🦋💅