about summary refs log tree commit diff
path: root/compiler/rustc_session/src/session.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2025-10-03 11:49:42 +0000
committerbors <bors@rust-lang.org>2025-10-03 11:49:42 +0000
commit8b6b15b877fbceb1ee5d9a5a4746e7515901574a (patch)
tree0301428b36812cac6a0647b40ce4be58757e4226 /compiler/rustc_session/src/session.rs
parentdd091003ace19d9556c647d87f7a9cd1e8dcc17e (diff)
parentc2a03cefd8899941032940df0c6be3b364de0ed0 (diff)
downloadrust-8b6b15b877fbceb1ee5d9a5a4746e7515901574a.tar.gz
rust-8b6b15b877fbceb1ee5d9a5a4746e7515901574a.zip
Auto merge of #142771 - dianqk:mir-stmt-debuginfo, r=cjgillot
Introduce debuginfo to statements in MIR

The PR introduces support for debug information within dead statements. Currently, only the reference statement is supported, which is sufficient to fix rust-lang/rust#128081.

I don't modify Stable MIR, as I don't think we need debug information when using it.

This PR represents the debug information for the dead reference statement via `#dbg_value`. For example, `let _foo_b = &foo.b` becomes `#dbg_value(ptr %foo, !22, !DIExpression(DW_OP_plus_uconst, 4, DW_OP_stack_value), !26)`. You can see this here: https://rust.godbolt.org/z/d43js6adv.

The general principle for handling debug information is to never provide less debug information than the optimized LLVM IR.

The current rules for dropping debug information in this PR are:

- If the LLVM IR cannot represent a reference address, it's replaced with poison or simply dropped. For example, see: https://rust.godbolt.org/z/shGqPec8W. I'm using poison in all such cases now.
- All debuginfos is dropped when merging multiple successor BBs. An example is available here: https://rust.godbolt.org/z/TE1q3Wq6M.

I doesn't drop debuginfos in `MatchBranchSimplification`, because LLVM also pick one branch for it.
Diffstat (limited to 'compiler/rustc_session/src/session.rs')
0 files changed, 0 insertions, 0 deletions