diff options
| -rw-r--r-- | examples/ramfunc.rs | 1 | ||||
| -rw-r--r-- | ui/task-priority-too-high.stderr | 2 |
2 files changed, 1 insertions, 2 deletions
diff --git a/examples/ramfunc.rs b/examples/ramfunc.rs index 54acd7e8..b3b8012c 100644 --- a/examples/ramfunc.rs +++ b/examples/ramfunc.rs @@ -1,6 +1,5 @@ //! examples/ramfunc.rs -#![deny(unsafe_code)] #![deny(warnings)] #![no_main] #![no_std] diff --git a/ui/task-priority-too-high.stderr b/ui/task-priority-too-high.stderr index 8b905c40..a7a15ebf 100644 --- a/ui/task-priority-too-high.stderr +++ b/ui/task-priority-too-high.stderr @@ -12,4 +12,4 @@ error[E0080]: evaluation of constant value failed 3 | #[rtic::app(device = lm3s6965)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at 'Maximum priority used by interrupt vector 'I2C0' is more than supported by hardware', $DIR/ui/task-priority-too-high.rs:3:1 | - = note: this error originates in the macro `$crate::panic::panic_2021` (in Nightly builds, run with -Z macro-backtrace for more info) + = note: this error originates in the macro `$crate::panic::panic_2021` which comes from the expansion of the macro `::core::panic` (in Nightly builds, run with -Z macro-backtrace for more info) |