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
50 lines
1.0 KiB
C++
50 lines
1.0 KiB
C++
// RUN: %clang_cc1 %s -triple x86_64-apple-darwin10 -O2 -emit-llvm -o - | FileCheck %s
|
|
// PR11480
|
|
|
|
void foo(int);
|
|
|
|
class A {
|
|
public:
|
|
A() { foo(1); }
|
|
};
|
|
|
|
class A1 {
|
|
public:
|
|
A1() { foo(2); }
|
|
};
|
|
|
|
class B {
|
|
public:
|
|
B() { foo(3); }
|
|
};
|
|
|
|
class C {
|
|
public:
|
|
static A a;
|
|
C() { foo(4); }
|
|
};
|
|
|
|
|
|
A C::a = A();
|
|
|
|
// CHECK: @llvm.global_ctors = appending global [3 x { i32, void ()* }] [{ i32, void ()* } { i32 200, void ()* @_GLOBAL__I_000200 }, { i32, void ()* } { i32 300, void ()* @_GLOBAL__I_000300 }, { i32, void ()* } { i32 65535, void ()* @_GLOBAL__sub_I_init_priority_attr.cpp }]
|
|
|
|
// CHECK: _GLOBAL__I_000200()
|
|
// CHECK: _Z3fooi(i32 3)
|
|
// CHECK-NEXT: ret void
|
|
|
|
// CHECK: _GLOBAL__I_000300()
|
|
// CHECK: _Z3fooi(i32 2)
|
|
// CHECK-NEXT: _Z3fooi(i32 1)
|
|
// CHECK-NEXT: ret void
|
|
|
|
// CHECK: _GLOBAL__sub_I_init_priority_attr.cpp()
|
|
// CHECK: _Z3fooi(i32 1)
|
|
// CHECK-NEXT: _Z3fooi(i32 4)
|
|
// CHECK-NEXT: ret void
|
|
|
|
C c;
|
|
A1 a1 __attribute__((init_priority (300)));
|
|
A a __attribute__((init_priority (300)));
|
|
B b __attribute__((init_priority (200)));
|