xtask sizes is incorrect with regards to the kernel
#474
Assignees
Labels
build
Affects or requires changes in the build system
developer-experience
Fixing this would have a positive impact on developer experience
Comments
steveklabnik
added
developer-experience
mkeeter
added a commit
that referenced
this issue
Jun 10, 2022
This PR implements task autosizing, at long last! It builds on the previous work with relocatable task builds (#584). After building the relocatable task ELF file, it runs a "dummy link" against a linker script with "infinite" memory (in practice, the entirety of memory available on the chip). It then parses the resulting (static) binary to extract sizes. After finding sizes for every task, it runs the same memory packer as before, then relinks each task with the resulting memory. Task sizes are based on the target microcontroller, with a new `alignment` parameter passed to `allocate_one`. There are extensive changes to `cargo xtask sizes` to make it more generically useful, decoupling the suggestions from the "find the size of a static ELF". WARNING: this changes the format of the exported JSON files! In addition, there are a bunch of new helper functions in `Config` to help with task and memory sizing / alignment. This fixes #474 and maybe #439, and deprecates #476
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The kernel doesn't require a power of two memory size, but
xtask sizesdoesn't know that, and so will give incorrect results.The text was updated successfully, but these errors were encountered: