| commit | 0dc7c6547eacba72b4e5e16dd23ecae2e6a9b053 | [log] [tgz] |
|---|---|---|
| author | Jeff Vander Stoep <[email protected]> | Wed Jan 31 19:55:11 2024 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Wed Jan 31 19:55:11 2024 +0000 |
| tree | 60ab42877b507a5508e7eb0bca613d8ef46ade79 | |
| parent | 4eb167967de93e5ec9aeec8f0815e3daf250f992 [diff] | |
| parent | ffc4a5b6cd3f1bb444e9dba28db7679c00aa8fc7 [diff] |
Upgrade atomic to 0.6.0 am: 839041b30b am: ffc4a5b6cd Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/atomic/+/2939603 Change-Id: Ie5edcb80b5d537c9e8ed7de82c0e62f26b4b2218 Signed-off-by: Automerger Merge Worker <[email protected]>
Atomic<T> for Rust
A Rust library which provides a generic Atomic<T> type for all T: NoUninit types, unlike the standard library which only provides a few fixed atomic types (AtomicBool, AtomicIsize, AtomicUsize, AtomicPtr). The NoUninit bound is from the bytemuck crate, and indicates that a type has no internal padding bytes. You will need to derive or implement this trait for all types used with Atomic<T>.
This library will use native atomic instructions if possible, and will otherwise fall back to a lock-based mechanism. You can use the Atomic::<T>::is_lock_free() function to check whether native atomic operations are supported for a given type. Note that a type must have a power-of-2 size and alignment in order to be used by native atomic instructions.
This crate uses #![no_std] and only depends on libcore.
Add this to your Cargo.toml:
[dependencies] atomic = "0.6"
and this to your crate root:
extern crate atomic;
Licensed under either of
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.