bdc969839a
This makes it easier to see where a global ctor comes from, and it also makes
ASan's init order analyzer output easier to understand. gcc does this too,
but only in -fPIC mode for some reason. Don't do this for constructors with
explicit init priority.
Also prepend "sub_" before the 'I', that way regular constructors stay
lexicographically after symbols with init priority (because
ord('s') > ord('I')). gold seems to ignore the name of constructor symbols,
and ld only looks at the symbol if it includes an init priority, which this
patch doesn't change.
Before: __GLOBAL_I_a
Now: __GLOBAL_sub_I_myfile.cc
llvm-svn: 208128
24 lines
571 B
C++
24 lines
571 B
C++
// RUN: %clang_cc1 -emit-llvm -g %s -o - | FileCheck %s
|
|
// rdar://problem/14985269.
|
|
//
|
|
// Verify that the global init helper function does not get associated
|
|
// with any source location.
|
|
//
|
|
// CHECK: define internal void @_GLOBAL__sub_I_globalinit_loc.cpp
|
|
// CHECK: !dbg ![[DBG:.*]]
|
|
// CHECK: "_GLOBAL__sub_I_globalinit_loc.cpp", i32 0, {{.*}}, i32 0} ; [ DW_TAG_subprogram ] [line 0] [local] [def]
|
|
// CHECK: ![[DBG]] = metadata !{i32 0, i32 0,
|
|
# 99 "someheader.h"
|
|
class A {
|
|
public:
|
|
A();
|
|
int foo() { return 0; }
|
|
};
|
|
# 5 "main.cpp"
|
|
A a;
|
|
|
|
int f() {
|
|
return a.foo();
|
|
}
|
|
|