diff options
| author | Hans Boehm <boehm@acm.org> | 2016-05-12 09:21:18 +0300 |
|---|---|---|
| committer | Ivan Maidanski <ivmai@mail.ru> | 2016-05-12 09:21:18 +0300 |
| commit | e558b28e2ce997075cbaf5cbf5f0c3da8a6b910a (patch) | |
| tree | 787e6eec14d3e1ca75a5ef9f7f4824860b3bc650 | |
| parent | e1cf751d418260da5384c38171a511999b0b82a0 (diff) | |
| download | libatomic_ops-e558b28e2ce997075cbaf5cbf5f0c3da8a6b910a.tar.gz | |
Refine documentation about _full memory ordering suffix
* doc/README.txt (_full): Refine documentation (regarding AO_nop_full
mostly).
| -rw-r--r-- | doc/README.txt | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/README.txt b/doc/README.txt index 62b3946..cf98bbf 100644 --- a/doc/README.txt +++ b/doc/README.txt @@ -160,7 +160,9 @@ _read: Subsequent reads must become visible after reads included in the atomic operation or preceding it. Rarely useful for clients? _write: Earlier writes become visible before writes during or after the atomic operation. Rarely useful for clients? -_full: Ordered with respect to both earlier and later memory ops. +_full: The associated operation is ordered with respect to both earlier and + later memory ops. If the associated operation is nop, then this orders + all earlier memory operations with respect to subsequent ones. AO_store_full or AO_nop_full are the normal ways to force a store to be ordered with respect to a later load. _release_write: Ordered with respect to earlier writes. This is |