[tock] Examine linker and linker flags for tock kernel and apps
Open
Nobody has claimed this yet.
Earlgrey-PROD Triaged
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
Examine the linker and linker flags being used to link the the tock kernel and apps.
Currently, I believe the OpenTitan rust configuration for riscv32 targets ends up using gnu ld to link code. Tock, on the other hand, normally expects llvm's lld to perform the final link stage.
- Determine how to alter our riscv32 toolchain such that
lldis the preferred linker. - Determine and appropriate set of flags to use when linking the tock kernel and apps.
Contributor guide
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
Start by tracing the OpenTitan riscv32 Rust toolchain configuration and comparing its current GNU ld behavior with Tock's expected LLVM lld final link stage. Determine the linker selection and flags needed for both the Tock kernel and apps, then validate that configuration in the relevant build flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100