summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Target/ARM/ARMISelLowering.cpp
diff options
context:
space:
mode:
authorTim Northover <tnorthover@apple.com>2013-10-24 10:37:09 +0000
committerTim Northover <tnorthover@apple.com>2013-10-24 10:37:09 +0000
commit94ecbd2e6c05316c25349eec88a99f40c83995ce (patch)
tree9f168acbd1099fe52eaeccd048b0f5951d3da3c0 /llvm/lib/Target/ARM/ARMISelLowering.cpp
parentb596fb2be2e436ac24162c284fdbe3fe6f69be3d (diff)
downloadbcm5719-llvm-94ecbd2e6c05316c25349eec88a99f40c83995ce.tar.gz
bcm5719-llvm-94ecbd2e6c05316c25349eec88a99f40c83995ce.zip
ARM: Use non-VFP softcalls on embedded Darwinish targets
The compiler-rt functions __adddf3vfp and so on exist purely to allow Thumb1 code to make use of VFP instructions by switching back to ARM mode, they make no sense for M-class processors which don't even have an ARM mode. Given that justification, in practice this is a platform ABI decision so the actual check is based on that rather than CPU features. rdar://problem/15302004 llvm-svn: 193327
Diffstat (limited to 'llvm/lib/Target/ARM/ARMISelLowering.cpp')
-rw-r--r--llvm/lib/Target/ARM/ARMISelLowering.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/lib/Target/ARM/ARMISelLowering.cpp b/llvm/lib/Target/ARM/ARMISelLowering.cpp
index 6214b472f90..43e3b3797d1 100644
--- a/llvm/lib/Target/ARM/ARMISelLowering.cpp
+++ b/llvm/lib/Target/ARM/ARMISelLowering.cpp
@@ -175,7 +175,7 @@ ARMTargetLowering::ARMTargetLowering(TargetMachine &TM)
setBooleanVectorContents(ZeroOrNegativeOneBooleanContent);
- if (Subtarget->isTargetDarwin()) {
+ if (Subtarget->isTargetIOS()) {
// Uses VFP for Thumb libfuncs if available.
if (Subtarget->isThumb() && Subtarget->hasVFP2()) {
// Single-precision floating-point arithmetic.
OpenPOWER on IntegriCloud