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
29 lines
586 B
C++
29 lines
586 B
C++
// RUN: %clang_cc1 -fms-extensions -fno-rtti -emit-llvm %s -o - -triple=i386-pc-win32 | FileCheck %s
|
|
|
|
// CHECK: @"\01??_7D@C@?1??foo@@YAXXZ@6B@" =
|
|
// CHECK: @"\01??_7B@?1??foo@A@@QAEXH@Z@6B@" =
|
|
// CHECK: define {{.*}} @"\01?baz@E@?3??bar@C@?1??foo@@YAXXZ@QAEXXZ@QAEXXZ"(
|
|
|
|
// Microsoft Visual C++ ABI examples.
|
|
struct A {
|
|
void foo (int) {
|
|
struct B { virtual ~B() {} };
|
|
B();
|
|
}
|
|
};
|
|
void foo () {
|
|
struct C {
|
|
struct D { virtual ~D() {} };
|
|
void bar () {
|
|
struct E {
|
|
void baz() { }
|
|
};
|
|
E().baz();
|
|
}
|
|
};
|
|
A().foo(0);
|
|
C::D();
|
|
C().bar();
|
|
}
|
|
|