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
472 B
C++
33 lines
472 B
C++
// RUN: %clang_cc1 -emit-llvm -triple %itanium_abi_triple -o - %s | FileCheck %s
|
|
|
|
struct A {
|
|
A() { x = 10; }
|
|
int x;
|
|
};
|
|
|
|
const A x;
|
|
|
|
// CHECK: @_ZL1x = internal global
|
|
|
|
struct X {
|
|
int (*fp)(int, int);
|
|
};
|
|
|
|
int add(int x, int y) { return x + y; }
|
|
|
|
// CHECK: @x2 = constant
|
|
extern const X x2;
|
|
const X x2 = { &add };
|
|
|
|
struct X1 {
|
|
mutable int i;
|
|
};
|
|
|
|
struct X2 {
|
|
X1 array[3];
|
|
};
|
|
|
|
// CHECK: @x2b = global
|
|
extern const X2 x2b;
|
|
const X2 x2b = { { { 1 }, { 2 }, { 3 } } };
|