Require optimization flag for codegen tests
Open
Nobody has claimed this yet.
A-compiletest
A-test-infra
A-testsuite
C-feature-request
T-bootstrap
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
New codegen tests often bounce on gnu-nopt. It would probably make sense to require that codegen tests explicitly specify -C opt-level.
Or possibly they should just always be run with optimizations unless explicitly overridden.
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 locating the Rust compiler's codegen test harness and the handling of gnu-nopt. Review how optimization flags are currently selected for these tests, then resolve whether tests must specify -C opt-level or should default to optimized runs. Done means the chosen policy is implemented and new codegen tests no longer bounce on gnu-nopt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100