Subject: [Boost-commit] svn:boost r84803 - trunk/libs/atomic/doc
From: andrey.semashev_at_[hidden]
Date: 2013-06-16 09:55:01
Author: andysem
Date: 2013-06-16 09:55:00 EDT (Sun, 16 Jun 2013)
New Revision: 84803
URL: http://svn.boost.org/trac/boost/changeset/84803
Log:
More docs updates.
Text files modified:
trunk/libs/atomic/doc/atomic.qbk | 18 +++++++++++++++---
1 files changed, 15 insertions(+), 3 deletions(-)
Modified: trunk/libs/atomic/doc/atomic.qbk
==============================================================================
--- trunk/libs/atomic/doc/atomic.qbk Sun Jun 16 09:46:39 2013 (r84802)
+++ trunk/libs/atomic/doc/atomic.qbk 2013-06-16 09:55:00 EDT (Sun, 16 Jun 2013) (r84803)
@@ -577,6 +577,10 @@
[table
[[Macro] [Description]]
[
+ [`BOOST_ATOMIC_FLAG_LOCK_FREE`]
+ [Indicate whether `atomic_flag` is lock-free]
+ ]
+ [
[`BOOST_ATOMIC_BOOL_LOCK_FREE`]
[Indicate whether `atomic<bool>` is lock-free]
]
@@ -620,6 +624,14 @@
[`BOOST_ATOMIC_ADDRESS_LOCK_FREE` or `BOOST_ATOMIC_POINTER_LOCK_FREE`]
[Indicate whether `atomic<T *>` is lock-free]
]
+ [
+ [`BOOST_ATOMIC_THREAD_FENCE`]
+ [Indicate whether `atomic_thread_fence` function is lock-free]
+ ]
+ [
+ [`BOOST_ATOMIC_SIGNAL_FENCE`]
+ [Indicate whether `atomic_signal_fence` function is lock-free]
+ ]
]
[endsect]
@@ -668,10 +680,10 @@
memory operations only in one direction. Since there is no
way to express this constraint to the compiler, these act
as "full compiler barriers" in this implementation. In corner
- cases this may lead to worse code than a C++11 compiler
+ cases this may result in a less efficient code than a C++11 compiler
could generate.
* [*No interprocess fallback]: using `atomic<T>` in shared memory only works
- correctly, if `atomic<T>::is_lock_free == true`
+ correctly, if `atomic<T>::is_lock_free() == true`
[endsect]
@@ -687,7 +699,7 @@
* [*native_api.cpp] verifies that all atomic operations have correct
value semantics (e.g. "fetch_add" really adds the desired value,
returning the previous). It is a rough "smoke-test" to help weed
- out the most obvious mistakes (for example with overflow,
+ out the most obvious mistakes (for example width overflow,
signed/unsigned extension, ...).
* [*lockfree.cpp] verifies that the [*BOOST_ATOMIC_*_LOCKFREE] macros
are set properly according to the expectations for a given