aboutsummaryrefslogtreecommitdiff
path: root/gcc/ada/gcc-interface/utils2.c
diff options
context:
space:
mode:
authorRichard Earnshaw <rearnsha@arm.com>2017-10-20 12:33:39 +0000
committerRichard Earnshaw <rearnsha@gcc.gnu.org>2017-10-20 12:33:39 +0000
commite64944ac65c3e0bb4115873f17b9c48f06c3813a (patch)
tree46cfe6bcfdeb5f89d75190f67fa79507e9e0abb7 /gcc/ada/gcc-interface/utils2.c
parentffa3ce5322226f094d3762ee5f32a5aab8b6a149 (diff)
downloadgcc-e64944ac65c3e0bb4115873f17b9c48f06c3813a.zip
gcc-e64944ac65c3e0bb4115873f17b9c48f06c3813a.tar.gz
gcc-e64944ac65c3e0bb4115873f17b9c48f06c3813a.tar.bz2
[arm] Fix architecture selection when building libatomic with automatic FPU selection
Libatomic builds a few functions for Arm with an explicit -march option. This option does not specify an FPU, which can lead to problems when targeting a hard-float or softfp environment since the architecture appears to be incompatible with the selected ABI. The fix is simple enough, just add +fp (the minimum floating point option) to the architecture. We don't use anything from the FP architecture, so it shouldn't really change anything; and if we are building for -mfloat-abi=soft the canonicalization process will remove the unnecessary fp attributes anyway. * Makefile.am: (IFUNC_OPTIONS): Set the architecture to -march=armv7-a+fp on Linux/Arm. * Makefile.in: Regenerated. From-SVN: r253935
Diffstat (limited to 'gcc/ada/gcc-interface/utils2.c')
0 files changed, 0 insertions, 0 deletions