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
34 lines
1.1 KiB
C++
34 lines
1.1 KiB
C++
// RUN: %clang_cc1 -fsyntax-only -triple %itanium_abi_triple -verify %s
|
|
// RUN: %clang_cc1 -fsyntax-only -triple %ms_abi_triple -DMSABI -verify %s
|
|
struct A {
|
|
virtual ~A();
|
|
};
|
|
|
|
struct B : A { // expected-error {{no suitable member 'operator delete' in 'B'}}
|
|
virtual void f();
|
|
|
|
void operator delete (void *, int); // expected-note {{'operator delete' declared here}}
|
|
};
|
|
|
|
#ifdef MSABI
|
|
B b; // expected-note {{implicit destructor for 'B' first required here}}
|
|
#else
|
|
void B::f() { // expected-note {{implicit destructor for 'B' first required here}}
|
|
}
|
|
#endif
|
|
|
|
struct C : A { // expected-error {{no suitable member 'operator delete' in 'C'}}
|
|
C();
|
|
void operator delete(void *, int); // expected-note {{'operator delete' declared here}}
|
|
};
|
|
|
|
C::C() { } // expected-note {{implicit destructor for 'C' first required here}}
|
|
|
|
struct D : A { // expected-error {{no suitable member 'operator delete' in 'D'}}
|
|
void operator delete(void *, int); // expected-note {{'operator delete' declared here}}
|
|
};
|
|
|
|
void f() {
|
|
new D; // expected-note {{implicit destructor for 'D' first required here}}
|
|
}
|