//! Nesting claims and how the preemption threshold works //! //! If you run this program you'll hit the breakpoints as indicated by the //! letters in the comments: A, then B, then C, etc. //! //! ``` //! #![deny(unsafe_code)] //! #![feature(proc_macro)] //! #![no_std] //! //! extern crate cortex_m_rtfm as rtfm; //! extern crate stm32f103xx; //! //! use stm32f103xx::Interrupt; //! use rtfm::{app, Resource, Threshold}; //! //! app! { //! device: stm32f103xx, //! //! resources: { //! static LOW: u64 = 0; //! static HIGH: u64 = 0; //! }, //! //! tasks: { //! EXTI0: { //! path: exti0, //! priority: 1, //! resources: [LOW, HIGH], //! }, //! //! EXTI1: { //! path: exti1, //! priority: 2, //! resources: [LOW], //! }, //! //! EXTI2: { //! path: exti2, //! priority: 3, //! resources: [HIGH], //! }, //! }, //! } //! //! fn init(_p: init::Peripherals, _r: init::Resources) {} //! //! fn idle() -> ! { //! // A //! rtfm::bkpt(); //! //! // Sets task `exti0` as pending //! // //! // Because `exti0` has higher priority than `idle` it will be executed //! // immediately //! rtfm::set_pending(Interrupt::EXTI0); // ~> exti0 //! //! loop { //! rtfm::wfi(); //! } //! } //! //! #[allow(non_snake_case)] //! fn exti0( //! t: &mut Threshold, //! EXTI0::Resources { mut LOW, mut HIGH }: EXTI0::Resources, //! ) { //! // Because this task has a priority of 1 the preemption threshold `t` also //! // starts at 1 //! //! // B //! rtfm::bkpt(); //! //! // Because `exti1` has higher priority than `exti0` it can preempt it //! rtfm::set_pending(Interrupt::EXTI1); // ~> exti1 //! //! // A claim creates a critical section //! LOW.claim_mut(t, |_low, t| { //! // This claim increases the preemption threshold to 2 //! // //! // 2 is just high enough to not race with task `exti1` for access to the //! // `LOW` resource //! //! // D //! rtfm::bkpt(); //! //! // Now `exti1` can't preempt this task because its priority is equal to //! // the current preemption threshold //! rtfm::set_pending(Interrupt::EXTI1); //! //! // But `exti2` can, because its priority is higher than the current //! // preemption threshold //! rtfm::set_pending(Interrupt::EXTI2); // ~> exti2 //! //! // F //! rtfm::bkpt(); //! //! // Claims can be nested //! HIGH.claim_mut(t, |_high, _| { //! // This claim increases the preemption threshold to 3 //! //! // Now `exti2` can't preempt this task //! rtfm::set_pending(Interrupt::EXTI2); //! //! // G //! rtfm::bkpt(); //! }); //! //! // Upon leaving the critical section the preemption threshold drops back //! // to 2 and `exti2` immediately preempts this task //! // ~> exti2 //! }); //! //! // Once again the preemption threshold drops but this time to 1. Now the //! // pending `exti1` task can preempt this task //! // ~> exti1 //! } //! //! fn exti1(_t: &mut Threshold, _r: EXTI1::Resources) { //! // C, I //! rtfm::bkpt(); //! } //! //! fn exti2(_t: &mut Threshold, _r: EXTI2::Resources) { //! // E, H //! rtfm::bkpt(); //! } //! ``` // Auto-generated. Do not modify. 19-tests Unnamed repository; edit this file 'description' to name the repository.
aboutsummaryrefslogtreecommitdiff
path: root/docs/ecosystem/react.md (unfollow)
AgeCommit message (Collapse)AuthorFilesLines
2023-10-09fix(AbortSignal/fetch) fix AbortSignal.timeout, fetch lock behavior and ↵Gravatar Ciro Spaciari 29-61/+303
fetch errors (#6390) * fix abort signal and fetch error * fix fetch error and lock behavior
2023-10-09Fix npm tag for canary bun-types, againGravatar Ashcon Partovi 2-56/+10
2023-10-09Add Fedora build instructions to development.md (#6359)Gravatar otterDeveloper 1-0/+10
2023-10-09added commands (#6314)Gravatar babar 1-1/+2
added commands to install unzip package and to check Linux kernel version
2023-10-09Update README.md (#6291)Gravatar TPLJ 1-1/+1
fixed some minor documentation.
2023-10-09docs: fixing a couple typos (#6331)Gravatar Michael Di Prisco 2-2/+2
2023-10-09fix: support uint8 exit code range (#6303)Gravatar Liz 2-2/+11
The exit code support is between 0-255 and not only in the signed positive range (0-127). Node.js does not seam to throw on a bigger integer and just wraps around, but throwing a error is a good approach and makes the behaviour more defined. This allows the range to be 0-255 Fixes: https://github.com/oven-sh/bun/issues/6284
2023-10-09Fix array variables preview in debugger (#6379)Gravatar 2hu 1-1/+4
2023-10-07feat(KeyObject) (#5940)Gravatar Ciro Spaciari 106-67/+9342
* oops * createSecretKey but weird error * use the right prototype, do not add a function called export lol * HMAC JWT export + base64 fix * Fix Equals, Fix Get KeySize, add complete export RSA * fix RSA export * add EC exports * X25519 and ED25519 export + fixes * fix default exports * better asymmetricKeyType * fix private exports * fix symmetricKeySize * createPublicKey validations + refactor * jwt + der fixes * oopsies * add PEM into createPublicKey * cleanup * WIP * bunch of fixes * public from private + private OKP * encrypted keys fixes * oops * fix clear tls error, add some support to jwk and other formats on publicEncrypt/publicDecrypt * more fixes and tests working * more fixes more tests * more clear hmac errors * more tests and fixes * add generateKeyPair * more tests passing, some skips * fix EC key from private * fix OKP JWK * nodejs ignores ext and key_ops on KeyObject.exports * add EC sign verify test * some fixes * add crypto.generateKeyPairSync(type, options) * more fixes and more tests * fix hmac tests * jsonwebtoken tests * oops * oops2 * generated files * revert package.json * vm tests * todos instead of failues * toBunString -> toString * undo simdutf * improvements * unlikely * cleanup * cleanup 2 * oops * move _generateKeyPairSync checks to native
2023-10-07Exclude more filesGravatar Jarred Sumner 1-1/+1
2023-10-07Exclude more filesGravatar Jarred Sumner 1-1/+2
2023-10-07Update settings.jsonGravatar Jarred Sumner 1-1/+2
2023-10-07Update settings.jsonGravatar Jarred Sumner 1-2/+3
2023-10-06fix a couple install testsGravatar Dylan Conway 1-8/+8
2023-10-06formatGravatar Dylan Conway 1-1/+2
2023-10-06Fix memory leak in fetch() (#6350)Gravatar Jarred Sumner 1-2/+0
Co-authored-by: Jarred Sumner <709451+Jarred-Sumner@users.noreply.github.com>
2023-10-06[types] allow onLoad plugin callbacks to return undefined (#6346)Gravatar Silver 1-1/+1
Returning undefined simply falls through to the next plugin, or to the default loader. This is defined by esbuild, and supported by Bun, but the types don't reflect it properly.
2023-10-06docs: `file.stream()` is not a promise (#6337)Gravatar Paul Nodet 1-1/+1