make incremental ICEs more informative
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.2k
- PR merge metrics
- PR metrics pending
Description
We are getting a couple of "compiler crashed spuriously due to incr comp, not reproducible" ICEs every week for years now.
https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AA-incr-comp
I wonder if we can print more data during/before the ice, if it occurs, to help us track down what the actual problem is.
So far the various stacktraces have not been too helpful without a clear reproducer afaik.
A similar approach made for a parallel compiler deadlock had great success https://github.com/rust-lang/rust/pull/118169/
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
Review the open A-incr-comp issues linked in the report and study PR #118169 for the analogous parallel compiler deadlock diagnostics. Identify what additional data would make incremental-compilation ICEs actionable, then verify that the resulting reports improve investigation of otherwise unreproducible crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100