c9bd88e681
This makes the C++ ABI depend entirely on the target: MS ABI for -win32 triples, Itanium otherwise. It's no longer possible to do weird combinations. To be able to run a test with a specific ABI without constraining it to a specific triple, new substitutions are added to lit: %itanium_abi_triple and %ms_abi_triple can be used to get the current target triple adjusted to the desired ABI. For example, if the test suite is running with the i686-pc-win32 target, %itanium_abi_triple will expand to i686-pc-mingw32. Differential Revision: http://llvm-reviews.chandlerc.com/D2545 llvm-svn: 199250
27 lines
654 B
C++
27 lines
654 B
C++
// RUN: %clang_cc1 -O1 -triple %itanium_abi_triple -emit-llvm -o - -fvisibility hidden %s | FileCheck %s
|
|
|
|
template<typename T>
|
|
struct X {
|
|
void f();
|
|
void g() { }
|
|
};
|
|
|
|
template<typename T> void X<T>::f() { }
|
|
|
|
extern template struct X<int>;
|
|
template struct X<int>;
|
|
extern template struct X<char>;
|
|
|
|
// <rdar://problem/8109763>
|
|
void test_X(X<int> xi, X<char> xc) {
|
|
// CHECK-LABEL: define weak_odr hidden {{.*}}void @_ZN1XIiE1fEv
|
|
xi.f();
|
|
// CHECK-LABEL: define weak_odr hidden {{.*}}void @_ZN1XIiE1gEv
|
|
xi.g();
|
|
// CHECK: declare {{.*}}void @_ZN1XIcE1fEv
|
|
xc.f();
|
|
// CHECK-LABEL: define available_externally {{.*}}void @_ZN1XIcE1gEv
|
|
xc.g();
|
|
}
|
|
|