Understand C11 Memory Ordering: relaxed, acquire, release, seq_cst

Atomics and Happens-Before

C11 stdatomic.h and C++ std::atomic expose memory_order_relaxed, acquire, release, and seq_cst. Lock-free stacks, queues, and reference counts rely on pairing release stores with acquire loads so published data is visible without mutex overhead. Getting ordering wrong produces bugs that reproduce only on ARM or under load.

Orders You Actually Need

relaxed for pure counters. release after writing payload, acquire before reading it. seq_cst is the safe default when learning; tighten later for performance.

cCopy
Loading…

• Data races on non-atomic fields remain undefined even with fences
• atomic_thread_fence is rarely needed when every access uses atomics
• x86 TSO is stronger than ARM; code that works on Intel may break on Apple silicon
• Use ThreadSanitizer when possible

Working Through the Exercise

Keep the relevant documentation open while you implement. When your output disagrees with the reference, trace one failing case by hand before changing random lines.

• Trace first: walk one failing input step by step
• Read the manual: skim the official doc for the mechanism named in this task
• Compare baselines: save measurements from the prior step so speedups are honest

Why for this exercise

You will implement a flag synchronization pattern using acquire/release atomics. This exercise asks you to publish a struct pointer safely without a mutex.