
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
24 lines
581 B
C++
24 lines
581 B
C++
// RUN: %clang_cc1 -std=c++11 -fno-rtti -emit-llvm %s -o - -triple=i386-pc-win32 | FileCheck %s
|
|
|
|
struct A {
|
|
constexpr A(int x) : x(x) {}
|
|
virtual void f();
|
|
int x;
|
|
};
|
|
|
|
A a(42);
|
|
// CHECK: @"\01?a@@3UA@@A" = global { [1 x i8*]*, i32 } { [1 x i8*]* @"\01??_7A@@6B@", i32 42 }, align 4
|
|
|
|
struct B {
|
|
constexpr B(int y) : y(y) {}
|
|
virtual void g();
|
|
int y;
|
|
};
|
|
|
|
struct C : A, B {
|
|
constexpr C() : A(777), B(13) {}
|
|
};
|
|
|
|
C c;
|
|
// CHECK: @"\01?c@@3UC@@A" = global { [1 x i8*]*, i32, [1 x i8*]*, i32 } { [1 x i8*]* @"\01??_7C@@6BA@@@", i32 777, [1 x i8*]* @"\01??_7C@@6BB@@@", i32 13 }
|