about summary refs log tree commit diff
path: root/src/test
diff options
context:
space:
mode:
authorWesley Wiser <wesleywiser@microsoft.com>2022-10-14 18:44:30 -0400
committerWesley Wiser <wesleywiser@microsoft.com>2022-10-14 18:44:30 -0400
commit34d90a46dac95d6f09cd8851b71b43350eecda4d (patch)
tree6ad3214cee7e870e3e2d02e7e54a8f78f2e0a146 /src/test
parent9363a1401e2d0061c810504c7be169badd5a910b (diff)
downloadrust-34d90a46dac95d6f09cd8851b71b43350eecda4d.tar.gz
rust-34d90a46dac95d6f09cd8851b71b43350eecda4d.zip
Fix line numbers for MIR inlined code
`should_collapse_debuginfo` detects if the specified span is part of a
macro expansion however it does this by checking if the span is anything
other than a normal (non-expanded) kind, then the span sequence is
walked backwards to the root span.

This doesn't work when the MIR inliner inlines code as it creates spans
with expansion information set to `ExprKind::Inlined` and results in the
line number being attributed to the inline callsite rather than the
normal line number of the inlined code.
Diffstat (limited to 'src/test')
-rw-r--r--src/test/codegen/mir-inlined-line-numbers.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/codegen/mir-inlined-line-numbers.rs b/src/test/codegen/mir-inlined-line-numbers.rs
index 53efe0f5be5..19d83f0eee7 100644
--- a/src/test/codegen/mir-inlined-line-numbers.rs
+++ b/src/test/codegen/mir-inlined-line-numbers.rs
@@ -20,6 +20,6 @@ pub fn example() {
 
 // CHECK-LABEL: @example
 // CHECK:   tail call void @bar(), !dbg [[DBG_ID:![0-9]+]]
-// CHECK: [[DBG_ID]] = !DILocation(line: 18, 
+// CHECK: [[DBG_ID]] = !DILocation(line: 7,
 // CHECK-SAME:                     inlinedAt: [[INLINE_ID:![0-9]+]])
 // CHECK: [[INLINE_ID]] = !DILocation(line: 18,