aboutsummaryrefslogtreecommitdiff
path: root/gcc/ada/gcc-interface/misc.c
diff options
context:
space:
mode:
authorSegher Boessenkool <segher@kernel.crashing.org>2020-11-06 12:50:35 +0000
committerSegher Boessenkool <segher@kernel.crashing.org>2020-11-06 22:14:15 +0000
commite5502ae72f784470019de5850017ad0c87ffacef (patch)
treed254623f3f895e9c2d8f1a0238e95db106405f54 /gcc/ada/gcc-interface/misc.c
parent6c8e4f4d79e1c6fb239616e4e07cb46a8c3eb81a (diff)
downloadgcc-e5502ae72f784470019de5850017ad0c87ffacef.zip
gcc-e5502ae72f784470019de5850017ad0c87ffacef.tar.gz
gcc-e5502ae72f784470019de5850017ad0c87ffacef.tar.bz2
rs6000: Fix TARGET_POWERPC64 vs. TARGET_64BIT confusion
I gave Ke Wen bad advice, luckily David corrected me: it is true that we cannot use TARGET_POWERPC64 on many 32-bit OSes, since either the kernel or userland does not save the top half of the 64-bit integer registers, but we do not have to care about that in separate patterns or related code. The flag is automatically not enabled by default on targets that do not handle this correctly. This patch fixes it. Segher 2020-11-06 Segher Boessenkool <segher@kernel.crashing.org> PR target/96933 * config/rs6000/rs6000.c (rs6000_expand_vector_init): Use TARGET_POWERPC64 instead of TARGET_64BIT.
Diffstat (limited to 'gcc/ada/gcc-interface/misc.c')
0 files changed, 0 insertions, 0 deletions