From: Ivan Maidanski Date: Mon, 14 Jan 2013 20:56:35 +0000 (+0400) Subject: Fix README regarding _acquire_read barrier X-Git-Tag: libatomic_ops-7_2e~18 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6e1617b18edb999810c3448c55867bcb00f9c881;p=libatomic_ops Fix README regarding _acquire_read barrier * doc/README.txt (_acquire_read): Add information about memory barrier (similar as in atomic_ops.h). * doc/README.txt (_release_read): Remove information about non-existing barrier. --- diff --git a/doc/README.txt b/doc/README.txt index 88445c0..7f7959e 100644 --- a/doc/README.txt +++ b/doc/README.txt @@ -159,6 +159,8 @@ _full: Ordered with respect to both earlier and later memory ops. _release_write: Ordered with respect to earlier writes. This is normally implemented as either a _write or _release barrier. +_acquire_read: Ordered with respect to later reads. This is + normally implemented as either a _read or _acquire barrier. _dd_acquire_read: Ordered with respect to later reads that are data dependent on this one. This is needed on a pointer read, which is later dereferenced to read a @@ -170,10 +172,6 @@ _dd_acquire_read: Ordered with respect to later reads that are data eliminate dependencies from the generated code, since dependencies force the hardware to execute the code serially.) -_release_read: Ordered with respect to earlier reads. Useful for - implementing read locks. Can be implemented as _release, - but not as _read, since _read groups the current operation - with the earlier ones. We assume that if a store is data-dependent on an a previous load, then the two are always implicitly ordered.