The Atomic Human

Game Rant: Where To Find The Atomic Lighter Deviant In Once Human

Diginomica: Meet The Atomic Human - a draft blueprint for trustworthy AI

22 Atomic vs. Non-Atomic Operations "An operation acting on shared memory is atomic if it completes in a single step relative to other threads. When an atomic store is performed on a shared memory, no other thread can observe the modification half-complete.

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 addition, accesses to atomic objects may establish inter-thread synchronization and order non-atomic memory accesses as specified by std::memory_order.

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 part of the value. Eg: The current Wikipedia article on First NF (Normal Form) section Atomicity actually quotes from the introductory parts above.

Its one thing I don't get about concurrency - threads and atomic-actions. According to docs.oracle these actions are specified as atomic: Reads and writes are atomic for reference variables and for...

The AVR-libc user manual in the section backs up my claim that 8-bit types on AVR, when compiled by gcc, already have naturally atomic reads and naturally atomic writes when it implies that 8-bit reads and writes are already atomic by saying (emphasis added):

Which types on a 64-bit computer are naturally atomic in gnu C and gnu ...