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
36 lines
783 B
C++
36 lines
783 B
C++
// RUN: %clang_cc1 %s -emit-llvm -triple %itanium_abi_triple -o - -fblocks | FileCheck %s
|
|
// rdar://8594790
|
|
|
|
struct A {
|
|
int x;
|
|
A(const A &);
|
|
A();
|
|
~A();
|
|
};
|
|
|
|
int main()
|
|
{
|
|
__block A BYREF_VAR;
|
|
^{ BYREF_VAR.x = 1234; };
|
|
return 0;
|
|
}
|
|
|
|
// CHECK-LABEL: define internal void @__Block_byref_object_copy_
|
|
// CHECK: call {{.*}} @_ZN1AC1ERKS_
|
|
// CHECK-LABEL: define internal void @__Block_byref_object_dispose_
|
|
// CHECK: call {{.*}} @_ZN1AD1Ev
|
|
// CHECK-LABEL: define internal void @__copy_helper_block_
|
|
// CHECK: call void @_Block_object_assign
|
|
// CHECK-LABEL: define internal void @__destroy_helper_block_
|
|
// CHECK: call void @_Block_object_dispose
|
|
|
|
// rdar://problem/11135650
|
|
namespace test1 {
|
|
struct A { int x; A(); ~A(); };
|
|
|
|
void test() {
|
|
return;
|
|
__block A a;
|
|
}
|
|
}
|