| Age | Commit message (Collapse) | Author |
|---|
|
I'm considering this a breaking change. I'll try to introduce new
sections that rely on the user's `unsafe` keyword for linker placement.
Rust 2024 has different opinions on format, and clippy has new thoughts.
Let's adopt them.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This development leftover should have been dropped after releasing
imxrt-ral 0.5.
|
|
|
|
The reset handler of 0.7.2 pushes four bytes onto the stack, resulting
in a misaligned stack pointer once the next procedure (main) is called.
Compilers are free to assume that the stack is eight byte aligned when
optimizing code. We depend on this reset handler, so this affects
imxrt-rt users.
Take the approach recommended in the cortex-m-rt advisory and update to
0.7.3. I tested this by building and running the two examples in this
repo on a 1010EVK. Also tested in imxrt-hal by building and running
examples on a 1010EVK.
cortex-m-rt 0.7.2 is yanked. Since imxrt-rt 0.1.0 fixes its cortex-m-rt
version, it will no longer build. I have no plan to also yank imxrt-rt
0.1.0; the upstream yank already signals that something is broken.
|
|
No need for us to set VTOR and the stack pointer anymore.
|
|
|
