rust/tests/codegen/mir-inlined-line-numbers.rs

// compile-flags: -O -g

#![crate_type = "lib"]

#[inline(always)]
fn foo() {
    bar();
}

#[inline(never)]
#[no_mangle]
fn bar() {
    panic!();
}

#[no_mangle]
pub fn example() {
    foo();
}

// CHECK-LABEL: @example
// CHECK:   tail call void @bar(), !dbg [[DBG_ID:![0-9]+]]
// CHECK: [[DBG_ID]] = !DILocation(line: 7,
// CHECK-SAME:                     inlinedAt: [[INLINE_ID:![0-9]+]])
// CHECK: [[INLINE_ID]] = !DILocation(line: 18,
Add test case for MIR inlining debuginfo line numbers 2022-10-14 13:09:30 -05:00			`// compile-flags: -O -g`

			`#![crate_type = "lib"]`

			`#[inline(always)]`
			`fn foo() {`
			`bar();`
			`}`

			`#[inline(never)]`
			`#[no_mangle]`
			`fn bar() {`
			`panic!();`
			`}`

			`#[no_mangle]`
			`pub fn example() {`
			`foo();`
			`}`

			`// CHECK-LABEL: @example`
			`// CHECK: tail call void @bar(), !dbg [[DBG_ID:![0-9]+]]`
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. 2022-10-14 17:44:30 -05:00			`// CHECK: [[DBG_ID]] = !DILocation(line: 7,`
Add test case for MIR inlining debuginfo line numbers 2022-10-14 13:09:30 -05:00			`// CHECK-SAME: inlinedAt: [[INLINE_ID:![0-9]+]])`
			`// CHECK: [[INLINE_ID]] = !DILocation(line: 18,`