oxidecomputer / oxidecomputer/bootleby
Toolchain upgrade
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Baseline
labbott@labbott-desktop2:~/bootleby$ arm-none-eabi-size target/thumbv8m.main-none-eabihf/release/bootleby
text data bss dec hex filename
2752 0 721988 724740 b0f04 target/thumbv8m.main-none-eabihf/release/bootleby
labbott@labbott-desktop2:~/bootleby$ git rev-parse HEAD
3e10edc514b47f31a3f97b2d4821ebe4c1d86115
bumping from 1.69.0 -> 1.77.0
labbott@labbott-desktop2:~/bootleby$ arm-none-eabi-size target/thumbv8m.main-none-eabihf/release/bootleby
text data bss dec hex filename
2804 0 721988 724792 b0f38 target/thumbv8m.main-none-eabihf/release/bootleby
This would let us bring in div_ceil, see #46 for more context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Find the repository's Rust toolchain declaration and update it from 1.69.0 to 1.77.0, checking issue #46 for the div_ceil context. Build the release target for thumbv8m.main-none-eabihf, then run arm-none-eabi-size and compare the result with the reported baseline; done means the upgrade builds and div_ceil is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, embedded-iot
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100