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
27 lines
619 B
C++
27 lines
619 B
C++
// RUN: %clang_cc1 -emit-llvm -triple %itanium_abi_triple %s -o - | FileCheck %s
|
|
template<typename T, typename U>
|
|
T* next(T* ptr, const U& diff);
|
|
|
|
template<typename T, typename U>
|
|
T* next(T* ptr, const U& diff) {
|
|
return ptr + diff;
|
|
}
|
|
|
|
void test(int *iptr, float *fptr, int diff) {
|
|
// CHECK: _Z4nextIiiEPT_S1_RKT0_
|
|
iptr = next(iptr, diff);
|
|
|
|
// CHECK: _Z4nextIfiEPT_S1_RKT0_
|
|
fptr = next(fptr, diff);
|
|
}
|
|
|
|
template<typename T, typename U>
|
|
T* next(T* ptr, const U& diff);
|
|
|
|
void test2(int *iptr, double *dptr, int diff) {
|
|
iptr = next(iptr, diff);
|
|
|
|
// CHECK: _Z4nextIdiEPT_S1_RKT0_
|
|
dptr = next(dptr, diff);
|
|
}
|