-
Notifications
You must be signed in to change notification settings - Fork 109
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
195: Add `no_std` implementation based on `critical-section`. r=matklad a=reitermarkus Add implementation based on `critical-section` for embedded targets. This started out using `critical_section::Mutex`, but tests were failing since `critical_section::with` blocks all threads during initialization, so I changed it to be basically the same as `imp_pl` without the `parking_lot` parts, since `atomic-polyfill` is based on `critical-section`. Depends on rust-embedded/critical-section#26. Co-authored-by: Markus Reiter <me@reitermark.us>
- Loading branch information
Showing
8 changed files
with
177 additions
and
51 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
use core::panic::{RefUnwindSafe, UnwindSafe}; | ||
|
||
use atomic_polyfill::{AtomicBool, Ordering}; | ||
use critical_section::{CriticalSection, Mutex}; | ||
|
||
use crate::unsync; | ||
|
||
pub(crate) struct OnceCell<T> { | ||
initialized: AtomicBool, | ||
// Use `unsync::OnceCell` internally since `Mutex` does not provide | ||
// interior mutability and to be able to re-use `get_or_try_init`. | ||
value: Mutex<unsync::OnceCell<T>>, | ||
} | ||
|
||
// Why do we need `T: Send`? | ||
// Thread A creates a `OnceCell` and shares it with | ||
// scoped thread B, which fills the cell, which is | ||
// then destroyed by A. That is, destructor observes | ||
// a sent value. | ||
unsafe impl<T: Sync + Send> Sync for OnceCell<T> {} | ||
unsafe impl<T: Send> Send for OnceCell<T> {} | ||
|
||
impl<T: RefUnwindSafe + UnwindSafe> RefUnwindSafe for OnceCell<T> {} | ||
impl<T: UnwindSafe> UnwindSafe for OnceCell<T> {} | ||
|
||
impl<T> OnceCell<T> { | ||
pub(crate) const fn new() -> OnceCell<T> { | ||
OnceCell { initialized: AtomicBool::new(false), value: Mutex::new(unsync::OnceCell::new()) } | ||
} | ||
|
||
pub(crate) const fn with_value(value: T) -> OnceCell<T> { | ||
OnceCell { | ||
initialized: AtomicBool::new(true), | ||
value: Mutex::new(unsync::OnceCell::with_value(value)), | ||
} | ||
} | ||
|
||
#[inline] | ||
pub(crate) fn is_initialized(&self) -> bool { | ||
self.initialized.load(Ordering::Acquire) | ||
} | ||
|
||
#[cold] | ||
pub(crate) fn initialize<F, E>(&self, f: F) -> Result<(), E> | ||
where | ||
F: FnOnce() -> Result<T, E>, | ||
{ | ||
critical_section::with(|cs| { | ||
let cell = self.value.borrow(cs); | ||
cell.get_or_try_init(f).map(|_| { | ||
self.initialized.store(true, Ordering::Release); | ||
}) | ||
}) | ||
} | ||
|
||
/// Get the reference to the underlying value, without checking if the cell | ||
/// is initialized. | ||
/// | ||
/// # Safety | ||
/// | ||
/// Caller must ensure that the cell is in initialized state, and that | ||
/// the contents are acquired by (synchronized to) this thread. | ||
pub(crate) unsafe fn get_unchecked(&self) -> &T { | ||
debug_assert!(self.is_initialized()); | ||
// SAFETY: The caller ensures that the value is initialized and access synchronized. | ||
self.value.borrow(CriticalSection::new()).get_unchecked() | ||
} | ||
|
||
#[inline] | ||
pub(crate) fn get_mut(&mut self) -> Option<&mut T> { | ||
self.value.get_mut().get_mut() | ||
} | ||
|
||
#[inline] | ||
pub(crate) fn into_inner(self) -> Option<T> { | ||
self.value.into_inner().into_inner() | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.