summaryrefslogtreecommitdiff
path: root/libgcc/configure
diff options
context:
space:
mode:
authorJoseph Myers <joseph@codesourcery.com>2014-10-25 01:22:02 +0100
committerJoseph Myers <jsm28@gcc.gnu.org>2014-10-25 01:22:02 +0100
commitd80c2beaf7d6f117fa52486f1006faec559fe1d2 (patch)
tree1cffab7659996d78e41096a87369aafe3f546bdb /libgcc/configure
parent0f849c161a29e9a5f73ae3d23e8d980119d53c9e (diff)
Optimize powerpc*-*-linux* 32-bit classic hard/soft float hardfp/soft-fp use.
Continuing the cleanups of libgcc soft-fp configuration for powerpc*-*-linux* in preparation for implementing TARGET_ATOMIC_ASSIGN_EXPAND_FENV for soft-float and e500, this patch optimizes the choice of which functions to build for the 32-bit classic hard-float and soft-float cases. (e500 will be dealt with in a separate patch which will need to add new features to t-hardfp and t-softfp; this patch keeps the status quo for e500.) For hard-float, while the functions in question are part of the libgcc ABI there is no need for them to contain software floating point code: no newly built code should use them, and if anything does use them it's most efficient (space and speed) for them to pass straight through to floating-point hardware instructions; this case is made to use t-hardfp to achieve that. For soft-float, direct use of soft-fp functions for operations involving DImode or unsigned integers is more efficient than using the libgcc2.c versions of those operations to convert to operations on other types (which then end up calling soft-fp functions for those other types, possibly more than once); this case is thus stopped from using t-softfp-excl. (A future patch will stop the e500 cases from using t-softfp-excl as well.) Tested with no regressions for crosses to powerpc-linux-gnu (soft float and classic hard float); also checked that the same set of symbols and versions is exported from shared libgcc before and after the patch. * configure.ac (ppc_fp_type): Set variable on powerpc*-*-linux*. * configure: Regenerate. * config.host (powerpc*-*-linux*): Use $ppc_fp_type to determine additions to tmake_file. Use t-hardfp-sfdf and t-hardfp instead of soft-fp for 32-bit classic hard float. Do not use t-softfp-excl for soft float. From-SVN: r216687
Diffstat (limited to 'libgcc/configure')
-rw-r--r--libgcc/configure23
1 files changed, 23 insertions, 0 deletions
diff --git a/libgcc/configure b/libgcc/configure
index 19c4ed69b19..7a154db9de9 100644
--- a/libgcc/configure
+++ b/libgcc/configure
@@ -4376,6 +4376,29 @@ fi
$as_echo "$libgcc_cv_mips_hard_float" >&6; }
esac
+# Determine floating-point type for powerpc*-*-linux*.
+# Single-precision-only FPRs are not a supported configuration for
+# this target, so are not allowed for in this test.
+case ${host} in
+powerpc*-*-linux*)
+ cat > conftest.c <<EOF
+#ifdef __powerpc64__
+ppc_fp_type=64
+#elif defined _SOFT_FLOAT
+ppc_fp_type=soft
+#elif defined _SOFT_DOUBLE
+ppc_fp_type=e500v1
+#elif defined __NO_FPRS__
+ppc_fp_type=e500v2
+#else
+ppc_fp_type=hard
+#endif
+EOF
+eval `${CC-cc} -E conftest.c | grep ppc_fp_type=`
+rm -f conftest.c
+;;
+esac
+
# Collect host-machine-specific information.
. ${srcdir}/config.host