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
33 lines
649 B
C++
33 lines
649 B
C++
// RUN: %clang_cc1 %s -triple %itanium_abi_triple -emit-llvm -o - | FileCheck %s
|
|
|
|
template<class T> class A {
|
|
public:
|
|
A() {}
|
|
virtual void a() {}
|
|
};
|
|
class B : A<int> {
|
|
B();
|
|
};
|
|
B::B() {}
|
|
|
|
template class A<long>;
|
|
|
|
extern template class A<short>;
|
|
template class A<short>;
|
|
|
|
|
|
// CHECK: @_ZTV1B = linkonce_odr unnamed_addr constant
|
|
// CHECK: @_ZTV1AIlE = weak_odr unnamed_addr constant
|
|
// CHECK: @_ZTV1AIsE = weak_odr unnamed_addr constant
|
|
// CHECK: @_ZTV1AIiE = linkonce_odr unnamed_addr constant
|
|
|
|
template<class T> struct C {
|
|
virtual void c() {}
|
|
};
|
|
struct D : C<int> {
|
|
virtual void d();
|
|
};
|
|
void D::d() {}
|
|
|
|
// CHECK: define {{.*}}@_ZN1CIiE1cEv(
|