mirror of
https://github.com/rust-lang/rust.git
synced 2024-12-11 16:15:03 +00:00
6f5b4e3581
We've investigated one reason why debugging information often goes wrong at https://reviews.llvm.org/D152095. > LLVM can't handle IR where subprogram definitions are nested within DICompositeType when doing LTO builds, > because there's no good way to cross the CU boundary to insert a nested DISubprogram definition in one CU into a type defined in another CU.
27 lines
909 B
Rust
27 lines
909 B
Rust
// compile-flags: -g -Cno-prepopulate-passes
|
|
|
|
// Verify that we added a declaration for a method.
|
|
|
|
// CHECK: define{{.*}}@method{{.*}} !dbg ![[METHOD_DEF_DBG:[0-9]+]]
|
|
// CHECK: define{{.*}}@function{{.*}} !dbg ![[FUNC_DEF_DBG:[0-9]+]]
|
|
|
|
#![crate_type = "lib"]
|
|
|
|
// CHECK-DAG: ![[FOO_DBG:[0-9]+]] = !DICompositeType(tag: {{.*}} name: "Foo", {{.*}} identifier:
|
|
pub struct Foo;
|
|
|
|
impl Foo {
|
|
// CHECK-DAG: ![[METHOD_DEF_DBG]] = distinct !DISubprogram(name: "method"{{.*}}, scope: ![[FOO_DBG]]{{.*}}DISPFlagDefinition{{.*}}, declaration: ![[METHOD_DECL_DBG:[0-9]+]]
|
|
// CHECK-DAG: ![[METHOD_DECL_DBG]] = !DISubprogram(name: "method"{{.*}}, scope: ![[FOO_DBG]]
|
|
#[no_mangle]
|
|
pub fn method() {}
|
|
}
|
|
|
|
// CHECK: ![[FUNC_DEF_DBG]] = distinct !DISubprogram(name: "function"
|
|
// CHECK-NOT: declaration
|
|
// CHECK-SAME: DISPFlagDefinition
|
|
// CHECK-NOT: declaration
|
|
// CHECK-SAME: )
|
|
#[no_mangle]
|
|
pub fn function() {}
|