5 releases (stable)
|1.0.3||Jul 11, 2023|
|1.0.2||Mar 12, 2023|
|1.0.1||Aug 12, 2022|
|0.1.11||Nov 29, 2022|
354,555 downloads per month
Used in 765 crates (19 directly)
⚠️ THIS CRATE IS DEPRECATED ⚠️
portable-atomic instead. It supports many more architectures and more efficient ways of emulating atomics.
portable-atomic with the
critical-section feature is a drop-in replacement. It uses the
critical-section crate to ensure locking, just like
However, if your chip is single-core, you might want to enable the
unsafe-assume-single-core feature instead. It makes
portable-atomic emulate atomics by disabling interrupts.
It is faster than using a
critical-section implementation that disables interrupts, because it allows disabling them only on CAS operations, not in load/store operations.
If you're writing a library, add a dependency on
portable-atomic but do NOT enable any feature on it. Let the end user of your library enable the right features for their target.
If you enable features, you're taking their choice away.
This crate polyfills atomics on targets where they're not available, using critical sections. It is intended to be a drop-in replacement for
There are two "levels" of polyfilling:
- Native: No polyfilling is performed, the native
- Full: Both load/store and compare-and-set operations are polyfilled.
Polyfilling requires a
critical-section implementation for the current target. Check the
critical-section README for details.
The right polyfill level is automatically picked based on the target and the atomic width:
|Target||Level||Level for u64/i64|
For targets not listed above,
atomic-polyfill assumes nothing and reexports
core::sync::atomic::*. No polyfilling is done. PRs for polyfilling more targets are welcome :)
Minimum Supported Rust Version (MSRV)
MSRV is currently Rust 1.54. MSRV may be upgraded at any new patch release as long as latest stable Rust is supported.
This work is licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
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.