Lines Matching refs:Atomic
9 [library Boost.Atomic
17 [purpose Atomic operations]
27 [section:introduction_presenting Presenting Boost.Atomic]
29 [*Boost.Atomic] is a library that provides [^atomic]
69 Atomic variables are useful for two purposes:
82 [section:thread_coordination Thread coordination using Boost.Atomic]
84 The most common use of [*Boost.Atomic] is to realize custom
109 [*Boost.Atomic] uses a synchronisation concept based on the
159 mapped to [*Boost.Atomic].
165 The most basic pattern for coordinating threads via [*Boost.Atomic]
244 [note Atomic fences are only indended to constraint ordering of
255 The second pattern for coordinating threads via [*Boost.Atomic]
329 The third pattern for coordinating threads via [*Boost.Atomic]
364 …lock pool used by [*Boost.Atomic] to implement lock-based atomic operations and waiting and notify…
366 Only has effect when building [*Boost.Atomic].]]
389 libraries, not just [*Boost.Atomic].]]
392 not just [*Boost.Atomic].]]
400 For example, you can build [*Boost.Atomic] with the following command line:
469 [section:interface_atomic_flag Atomic flags]
546 define the default constructor. Thus the closest equivalent C++03 code using [*Boost.Atomic]
563 [section:interface_atomic_object Atomic objects]
584 [*Boost.Atomic] attempts to support operations on floating point types on some
678 The `value` operation is a [*Boost.Atomic] extension. The returned reference can be used to invoke …
679 on the atomic value, which are not part of [*Boost.Atomic] but are compatible with it on the target…
732 Additionally, as a [*Boost.Atomic] extension, the following operations are also provided:
842 [note In [*Boost.Atomic] 1.66 the [^['op]_and_test] operations returned the opposite value (i.e. `t…
843 to the current behavior in 1.67 for consistency with other operations in [*Boost.Atomic], as well a…
844 [*Boost.Atomic] 1.66 was the only release shipped with the old behavior.]
885 Additionally, as a [*Boost.Atomic] extension, the following operations are also provided:
930 When using atomic operations with floating point types, bear in mind that [*Boost.Atomic]
966 Similarly to integers, the following [*Boost.Atomic] extensions are also provided:
1080 [section:interface_atomic_ref Atomic references]
1096 than the natural alignment of type [^['T]]. In [*Boost.Atomic], `required_alignment` indicates
1149 …Shall not be less than [^alignof(['T])]. In [*Boost.Atomic], indicates the alignment required by l…
1180 the object value. Typically, padding bits are used for alignment purposes. [*Boost.Atomic] does not…
1186 Padding bits pose a problem for [*Boost.Atomic] because they can break binary comparison of object …
1223 …ke C++20, the `wait` operation returns ['T] instead of `void`. This is a [*Boost.Atomic] extension.
1242 …notifying operations may involve locking and require linking with [*Boost.Atomic] compiled library.
1248 [section:interface_ipc Atomic types for inter-process communication]
1254 [*Boost.Atomic] provides a dedicated set of types for inter-process communication: `boost::ipc_atom…
1299 [*Boost.Atomic] defines a number of macros to allow compile-time
1367 In addition to these standard macros, [*Boost.Atomic] also defines a number of extension macros,
1448 While [*Boost.Atomic] strives to implement the atomic operations
1452 * [*Aggregate initialization syntax is not supported]: Since [*Boost.Atomic]
1457 [*Boost.Atomic] does support direct and unified initialization syntax though.
1470 as required in C++11. [*Advice]: In C++03, do not use [*Boost.Atomic] in contexts
1481 for example). In the current implementation [*Boost.Atomic] follows that trend,
1494 could generate. [*Boost.Atomic] will use compiler intrinsics, if possible,
1496 * [*Atomic operations may enforce "too strong" memory ordering in debug mode]:
1507 representation]: [*Boost.Atomic] makes this requirement in order to implement
1510 arithmetics, which means that [*Boost.Atomic] has to operate on unsigned integers internally
1515 this section], [*Boost.Atomic] cannot support types with padding bits because their content
1518 …ther operations are built upon these, potentially all operations become unreliable. [*Boost.Atomic]
1528 [*Boost.Atomic] provides a unit test suite to verify that the
1576 [*Boost.Atomic] has been tested on and is known to work on