diff options
| author | Ivan Maidanski <ivmai@mail.ru> | 2013-01-15 00:56:35 +0400 |
|---|---|---|
| committer | Ivan Maidanski <ivmai@mail.ru> | 2013-01-15 00:56:35 +0400 |
| commit | 05be2208cc9d70e338f2e9e6d556c010c066a2e3 (patch) | |
| tree | c2d5f22e029dae585a965cd0c91f3dd6e87a259a /doc | |
| parent | 17a67a4dece3c48f4e1bc8c95be90056aafd6a8c (diff) | |
| download | libatomic_ops-05be2208cc9d70e338f2e9e6d556c010c066a2e3.tar.gz | |
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.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/README.txt | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/README.txt b/doc/README.txt index 348247d..0047092 100644 --- a/doc/README.txt +++ b/doc/README.txt @@ -166,6 +166,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 @@ -177,10 +179,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. |