rust-lang / rust-lang/rustc-perf
Gather more detailed statistics for bootstrap timings
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 732
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
Currently, we only record the total build time for each crate in the 'bootstrap timings' section. Would it be possible to build the compiler while capturing the same level of detail as we do for other benchmaks? (e.g. self-profile information)? If this adds too much overhead, the output of -Z time-passes would still be very useful.
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
No files or tests are named. Start by locating the implementation of the “bootstrap timings” section and compare it with the existing benchmark profiling path, especially self-profile and -Z time-passes output. Done means compiler builds report more detailed per-stage timing data without unacceptable overhead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100