diff options
author | Ivan Maidanski <ivmai@mail.ru> | 2011-10-21 13:46:01 +0400 |
---|---|---|
committer | Ivan Maidanski <ivmai@mail.ru> | 2011-10-21 13:54:44 +0400 |
commit | 90373195033cb8efac5d3dee55be2ef8c3c3def4 (patch) | |
tree | d6583a3dcb9149507cf3bfd8ecdb6fd13bc47fed | |
parent | de0f8550e3f76e4c3b79d5024f816ca171756720 (diff) | |
download | libatomic_ops-90373195033cb8efac5d3dee55be2ef8c3c3def4.tar.gz |
Fix a typo in doc/README.txt
-rw-r--r-- | doc/README.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/README.txt b/doc/README.txt index 989a70f..88445c0 100644 --- a/doc/README.txt +++ b/doc/README.txt @@ -137,7 +137,7 @@ ORDERING CONSTRAINTS: Each operation name also includes a suffix that specifies the associated ordering semantics. The ordering constraint limits reordering of this -operation with repsect to other atomic operations and ordinary memory +operation with respect to other atomic operations and ordinary memory references. The current implementation assumes that all memory references are to ordinary cacheable memory; the ordering guarantee is with respect to other threads or processes, not I/O devices. (Whether or not this @@ -153,7 +153,7 @@ _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 memops. +_full: Ordered with respect to both earlier and later memory ops. 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 |