rust-lang / rust-lang/rustc-perf
Support parallel front end test in rustc-perf
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 733
- Forks
- 189
- Avg merge
- 10h 52m
- Merged PRs (30d)
- 43
Description
Parallel front end is an important means to improve compiler performance, but currently we cannot use rustc-perf to test the impact on the compiler performance of the parallelized front end in a PR.
We should support the -Z threads=n compiler option when compiling the use cases in the bot to compare the impact of code changes in PRs on the parallelization frontend.
updates #118698
updates #113349
cc @Kobzol @jieyouxu
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
Start by tracing how rustc-perf's bot compiles benchmark use cases and passes compiler options. Check how existing rustc flags are configured, then determine where -Z threads=n must be supported for PR comparisons. Done means the bot can benchmark parallel front-end configurations and compare their compiler performance impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100