summaryrefslogtreecommitdiffstats
path: root/clang/lib/Basic/Targets.cpp
diff options
context:
space:
mode:
authorOliver Stannard <oliver.stannard@arm.com>2015-09-03 11:46:24 +0000
committerOliver Stannard <oliver.stannard@arm.com>2015-09-03 11:46:24 +0000
commit9253f00d135685e00661e9b3627e537ba5d046ae (patch)
treeefa26115c7d1881898ec358d21c49be1ab1e4f7e /clang/lib/Basic/Targets.cpp
parentd0f83d15a35f7935e8ca7aa54675ef250e91fe3e (diff)
downloadbcm5719-llvm-9253f00d135685e00661e9b3627e537ba5d046ae.tar.gz
bcm5719-llvm-9253f00d135685e00661e9b3627e537ba5d046ae.zip
Revert 246755 as it breaks buildbots
Original commit message: [ARM] Allow passing/returning of __fp16 arguments The ACLE (ARM C Language Extensions) 2.0 allows the __fp16 type to be used as a functon argument or return type (ACLE 1.1 did not). The current public release of the AAPCS (2.09) states that __fp16 values should be converted to single-precision before being passed or returned, but AAPCS 2.10 (to be released shortly) changes this, so that they are passed in the least-significant 16 bits of either a GPR (for base AAPCS) or a single-precision register (for AAPCS-VFP). This does not change how arguments are passed if they get passed on the stack. This patch brings clang up to compliance with the latest versions of both of these specs. We can now set the __ARM_FP16_ARGS ACLE predefine, and we have always been able to set the __ARM_FP16_FORMAT_IEEE predefine (we do not support the alternative format). llvm-svn: 246760
Diffstat (limited to 'clang/lib/Basic/Targets.cpp')
-rw-r--r--clang/lib/Basic/Targets.cpp4
1 files changed, 0 insertions, 4 deletions
diff --git a/clang/lib/Basic/Targets.cpp b/clang/lib/Basic/Targets.cpp
index bc204b6b3ba..77cce95dca2 100644
--- a/clang/lib/Basic/Targets.cpp
+++ b/clang/lib/Basic/Targets.cpp
@@ -4568,10 +4568,6 @@ public:
// ACLE predefines.
Builder.defineMacro("__ARM_ACLE", "200");
- // FP16 support (we currently only support IEEE format).
- Builder.defineMacro("__ARM_FP16_FORMAT_IEEE", "1");
- Builder.defineMacro("__ARM_FP16_ARGS", "1");
-
// Subtarget options.
// FIXME: It's more complicated than this and we don't really support
OpenPOWER on IntegriCloud