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
25 lines
537 B
C++
25 lines
537 B
C++
// RUN: %clang_cc1 -triple %itanium_abi_triple -emit-llvm %s -o -
|
|
|
|
// FIXME: Don't assert for non-Win32 triples (PR18251).
|
|
// RUN: %clang_cc1 -triple i686-pc-win32 -fno-rtti -emit-llvm %s -o -
|
|
|
|
struct A {
|
|
virtual void Method() = 0;
|
|
};
|
|
|
|
struct B : public A {
|
|
virtual void Method() { }
|
|
};
|
|
|
|
typedef void (A::*fn_type_a)(void);
|
|
typedef void (B::*fn_type_b)(void);
|
|
|
|
int main(int argc, char **argv)
|
|
{
|
|
fn_type_a f = reinterpret_cast<fn_type_a>(&B::Method);
|
|
fn_type_b g = reinterpret_cast<fn_type_b>(f);
|
|
B b;
|
|
(b.*g)();
|
|
return 0;
|
|
}
|