7232f66051
Summary: Clang does not detect `aapcs-vfp` for the EABIHF environment. The reason is that only GNUEABIHF is considered while choosing calling convention, EABIHF is ignored. This causes clang to use `aapcs` for EABIHF and add the `arm_aapcscc` specifier to functions in generated IR. The modified `arm-cc.c` test checks that no calling convention specifier is added to functions for EABIHF, which means the default one is used (`CallingConv::ARM_AAPCS_VFP`). Reviewers: rengolin, compnerd, t.p.northover Subscribers: aemerson, rengolin, asl, cfe-commits Differential Revision: http://reviews.llvm.org/D20219 llvm-svn: 269419
24 lines
1.2 KiB
C
24 lines
1.2 KiB
C
// REQUIRES: arm-registered-target
|
|
// RUN: %clang_cc1 -triple armv7-apple-darwin9 -target-abi apcs-gnu -emit-llvm -w -o - %s | FileCheck -check-prefix=DARWIN-APCS %s
|
|
// RUN: %clang_cc1 -triple armv7-apple-darwin9 -target-abi aapcs -emit-llvm -w -o - %s | FileCheck -check-prefix=DARWIN-AAPCS %s
|
|
// RUN: %clang_cc1 -triple arm-none-linux-gnueabi -target-abi apcs-gnu -emit-llvm -w -o - %s | FileCheck -check-prefix=LINUX-APCS %s
|
|
// RUN: %clang_cc1 -triple arm-none-linux-gnueabi -target-abi aapcs -emit-llvm -w -o - %s | FileCheck -check-prefix=LINUX-AAPCS %s
|
|
// RUN: %clang_cc1 -triple armv7-none-eabihf -target-abi aapcs-vfp -emit-llvm -w -o - %s | FileCheck -check-prefix=BAREMETAL-AAPCS_VFP %s
|
|
|
|
|
|
// DARWIN-APCS-LABEL: define void @f()
|
|
// DARWIN-APCS: call void @g
|
|
// DARWIN-AAPCS-LABEL: define arm_aapcscc void @f()
|
|
// DARWIN-AAPCS: call arm_aapcscc void @g
|
|
// LINUX-APCS-LABEL: define arm_apcscc void @f()
|
|
// LINUX-APCS: call arm_apcscc void @g
|
|
// LINUX-AAPCS-LABEL: define void @f()
|
|
// LINUX-AAPCS: call void @g
|
|
// BAREMETAL-AAPCS_VFP-LABEL: define void @f()
|
|
// BAREMETAL-AAPCS_VFP: call void @g
|
|
// BAREMETAL-AAPCS_VFP: declare void @g()
|
|
void g(void);
|
|
void f(void) {
|
|
g();
|
|
}
|