rust-lang / rust-lang/rustc-perf
Binary size on multiple targets
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 733
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
Based on https://github.com/rust-lang/wg-binary-size/issues/3, we would like to see binary size outputs on a few different targets show up as perf results. Just checking output size should be relatively fast compared to benchmarking so we can probably include any std targets that we can cross compile to, as well as something WASM and a few popular no_std targets.
It would be extra nice if the report could hold expanded details about the size of each section, but that is a bonus rather than a core feature.
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
The issue names no files, tests, or entry points. Start by reading the linked rust-lang/wg-binary-size issue and locating how rustc-perf records and reports performance results. Done means reporting binary sizes for several cross-compiled std, WASM, and no_std targets, with section details as an optional enhancement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100