Aug 13, 2015 · Objects of atomic types are the only C++ objects that are free from data races; that is, if one thread writes to an atomic object while another thread reads from it, the behavior is well-defined. …

In the Effective Java book, it states: The language specification guarantees that reading or writing a variable is atomic unless the variable is of type long or double [JLS, 17.4.7]. What do...

Jan 23, 2025 · At least atomic<shared_ptr<T>> gives you per-object locking, instead of a single lock for the whole stack. So multiple threads can be waiting for different locks if multiple pops start in parallel.

@CygnusX1 yes, that is covered in the C++ standard by the rest of the note, which OP left out of the quote: "When a compare-and-exchange is in a loop, the weak version will yield better performance …

Jun 19, 2025 · 2 We are currently evaluating 128-bit atomic operation support across platforms and compilers, and I wanted to confirm the level of support available in Clang specifically. Our reference …

The reason num++ appears to be atomic is because on x86 machines, incrementing a 32-bit integer is, in fact, atomic (assuming no memory retrieval takes place). But this is neither guaranteed by the c++ …

Apr 30, 2016 · I remember I came across certain types in the C language called atomic types, but we have never studied them. So, how do they differ from regular types like int,float,double,long etc., and …

Jan 16, 2024 · @anatolyg if waiting through std::atomic_bool::wait is somehow inferior to waiting on std::condition_variable, then that'd be a reason to use the old version, at least in some cases. It's a …

Oct 20, 2014 · Why the standard make that difference? It seems as both designate, in the same way, an atomic type.

Jun 4, 2014 · The definition of atomic is hazy; a value that is atomic in one application could be non-atomic in another. For a general guideline, a value is non-atomic if the application deals with only a …