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
34 lines
995 B
C
34 lines
995 B
C
// RUN: %clang_cc1 -emit-llvm %s -o - -triple=i386-pc-win32 | FileCheck %s
|
|
// RUN: %clang_cc1 -emit-llvm %s -o - -triple=i386-mingw32 | FileCheck %s
|
|
|
|
void __stdcall f1(void) {}
|
|
// CHECK: define x86_stdcallcc void @"\01_f1@0"
|
|
|
|
void __fastcall f2(void) {}
|
|
// CHECK: define x86_fastcallcc void @"\01@f2@0"
|
|
|
|
void __stdcall f3() {}
|
|
// CHECK: define x86_stdcallcc void @"\01_f3@0"
|
|
|
|
void __fastcall f4(char a) {}
|
|
// CHECK: define x86_fastcallcc void @"\01@f4@4"
|
|
|
|
void __fastcall f5(short a) {}
|
|
// CHECK: define x86_fastcallcc void @"\01@f5@4"
|
|
|
|
void __fastcall f6(int a) {}
|
|
// CHECK: define x86_fastcallcc void @"\01@f6@4"
|
|
|
|
void __fastcall f7(long a) {}
|
|
// CHECK: define x86_fastcallcc void @"\01@f7@4"
|
|
|
|
void __fastcall f8(long long a) {}
|
|
// CHECK: define x86_fastcallcc void @"\01@f8@8"
|
|
|
|
void __fastcall f9(long long a, char b, char c, short d) {}
|
|
// CHECK: define x86_fastcallcc void @"\01@f9@20"(i64 %a, i8 signext %b, i8
|
|
// signext %c, i16 signext %d)
|
|
|
|
void f12(void) {}
|
|
// CHECK: define void @f12(
|