Portable atomic types including support for 128-bit atomics, atomic float, etc.
Atomic{I,U}{8,16,32,64}
) for all targets that can use atomic CAS. (i.e., all targets that can use std
, and most no-std targets)AtomicI128
and AtomicU128
.AtomicF32
and AtomicF64
. (optional)
Native 128-bit atomic operations are available on x86_64 (Rust 1.59+), aarch64 (Rust 1.59+), and s390x (nightly only), otherwise the fallback implementation is used.
On x86_64, when the outline-atomics
optional feature is not enabled and cmpxchg16b
target feature is not enabled at compile-time, this uses the fallback implementation. cmpxchg16b
target feature is enabled by default only on macOS.
fallback
(enabled by default)
Enable fallback implementations.
Disabling this allows only atomic types for which the platform natively supports atomic operations.
outline-atomics
Enable run-time CPU feature detection.
This allows maintaining support for older CPUs while using features that are not supported on older CPUs, such as cmpxchg16b (x86_64) and LSE (aarch64).
Note:
std
).float
Provide AtomicF{32,64}
.
Note that most of fetch_*
operations of atomic floats are implemented using CAS loops, which can be slower than equivalent operations of atomic integers.
std
Use std
.
serde
Implement serde::{Serialize,Deserialize}
for atomic types.
Note:
--cfg portable_atomic_unsafe_assume_single_core
Assume that the target is single-core.
When this cfg is enabled, this crate provides atomic CAS for targets where atomic CAS is not available in the standard library.
Note: This cfg is unsafe
, and enabling this cfg for multi-core systems is unsound.
This is intentionally not an optional feature. (If this is an optional feature, dependencies can implicitly enable the feature, resulting in the use of unsound code without the end-user being aware of it.)
Enabling this cfg for targets that have atomic CAS will result in a compile error.
Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.