docs/devel/atomics.rst

19 and atomic operations.  The semantics of concurrent memory accesses are governed
298 either *acquire* or *release* semantics\ [#rmw]_.  This has two effects:
312 The concept of acquire and release semantics is not exclusive to atomic
314 acquire or release semantics.  For example:
316 - ``pthread_mutex_lock`` has acquire semantics, ``pthread_mutex_unlock`` has
317   release semantics and synchronizes with a ``pthread_mutex_lock`` for the
320 - ``pthread_cond_signal`` and ``pthread_cond_broadcast`` have release semantics;
321   ``pthread_cond_wait`` has both release semantics (synchronizing with
322   ``pthread_mutex_lock``) and acquire semantics (synchronizing with
325 - ``pthread_create`` has release semantics and synchronizes with the start
326   of the new thread; ``pthread_join`` has acquire semantics and synchronizes
329 - ``qemu_event_set`` has release semantics, ``qemu_event_wait`` has
330   acquire semantics.
389 Acquire and release semantics of higher-level primitives can also be
431   semantics via ``ACCESS_ONCE`` (or the more recent ``READ``/``WRITE_ONCE``).
434   semantics if the compiler supports it, and volatile semantics otherwise.
435   Both semantics prevent the compiler from doing certain transformations;