From: Ivan Maidanski Date: Fri, 21 Oct 2011 09:46:01 +0000 (+0400) Subject: Fix a typo in doc/README.txt X-Git-Tag: libatomic_ops-7_3alpha2~70 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=855780c5ed34725f74681e6f8a1fd38448a82b61;p=libatomic_ops Fix a typo in doc/README.txt --- 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