rust-lang / rust-lang/rustc_codegen_cranelift
Jitted runs do not terminate cleanly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 157
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 3
Description
Because rustc_codegen_cranelift::driver::jit::run_jit never returns, rustc never runs finalisation actions for jitted runs; e.g. the incremental compilation cache is not committed to disk (in particular, rustc_interface::interface::Compiler::enter never progresses from invoking the passed f closure to the subsequent save_dep_graph call).
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 in src/driver/jit.rs at rustc_codegen_cranelift::driver::jit::run_jit, then read rustc_interface::interface::Compiler::enter in compiler/rustc_interface/src/queries.rs. Trace why the JIT path does not return and verify that finalisation reaches the subsequent save_dep_graph call so the incremental cache is committed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100