summaryrefslogtreecommitdiffstats
path: root/share
diff options
context:
space:
mode:
authorjhb <jhb@FreeBSD.org>2009-05-21 13:39:46 +0000
committerjhb <jhb@FreeBSD.org>2009-05-21 13:39:46 +0000
commit57032de649ec2affb1a0c8d482e19007f8e8916f (patch)
tree4780bbddc2797edcb8c719d0516c5906e6ae083f /share
parent68353e273feaeabea942a8eaeeebda9412574dec (diff)
downloadFreeBSD-src-57032de649ec2affb1a0c8d482e19007f8e8916f.zip
FreeBSD-src-57032de649ec2affb1a0c8d482e19007f8e8916f.tar.gz
Attempt to clarify some confusing wording regarding atomic_load() and
atomic_store().
Diffstat (limited to 'share')
-rw-r--r--share/man/man9/atomic.94
1 files changed, 2 insertions, 2 deletions
diff --git a/share/man/man9/atomic.9 b/share/man/man9/atomic.9
index 70ee2ab..0bc567c 100644
--- a/share/man/man9/atomic.9
+++ b/share/man/man9/atomic.9
@@ -225,7 +225,7 @@ return (*addr)
.Pp
The
.Fn atomic_load
-functions always have acquire semantics.
+functions are only provided with acquire memory barriers.
.Bl -hang
.It Fn atomic_readandclear addr
.Bd -literal -compact
@@ -263,7 +263,7 @@ not have any variants with memory barriers at this time.
.Pp
The
.Fn atomic_store
-functions always have release semantics.
+functions are only provided with release memory barriers.
.Pp
The type
.Dq Li 64
OpenPOWER on IntegriCloud