
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
31 lines
747 B
C++
31 lines
747 B
C++
// RUN: %clang_cc1 -S -emit-llvm -triple %itanium_abi_triple -o - %s -finstrument-functions | FileCheck %s
|
|
|
|
// CHECK: @_Z5test1i
|
|
int test1(int x) {
|
|
// CHECK: __cyg_profile_func_enter
|
|
// CHECK: __cyg_profile_func_exit
|
|
// CHECK: ret
|
|
return x;
|
|
}
|
|
|
|
// CHECK: @_Z5test2i
|
|
int test2(int) __attribute__((no_instrument_function));
|
|
int test2(int x) {
|
|
// CHECK-NOT: __cyg_profile_func_enter
|
|
// CHECK-NOT: __cyg_profile_func_exit
|
|
// CHECK: ret
|
|
return x;
|
|
}
|
|
|
|
// This test case previously crashed code generation. It exists solely
|
|
// to test -finstrument-function does not crash codegen for this trivial
|
|
// case.
|
|
namespace rdar9445102 {
|
|
class Rdar9445102 {
|
|
public:
|
|
Rdar9445102();
|
|
};
|
|
}
|
|
static rdar9445102::Rdar9445102 s_rdar9445102Initializer;
|
|
|