procyberian/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

rs6000: Fix TARGET_POWERPC64 vs. TARGET_64BIT confusion

Browse source 
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.
This commit is contained in:
Segher Boessenkool 2020-11-06 12:50:35 +00:00
parent 6c8e4f4d79
commit e5502ae72f
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
gcc/config/rs6000/rs6000.c
View file

@ -6799,7 +6799,7 @@ rs6000_expand_vector_init (rtx target, rtx vals)
for (i = 0; i < n_elts; i++)
{
rtx tmp = force_reg (GET_MODE_INNER (mode), XVECEXP (vals, 0, i));
if (TARGET_64BIT)
if (TARGET_POWERPC64)
{
op[i] = gen_reg_rtx (DImode);
emit_insn (gen_zero_extendqidi2 (op[i], tmp));
@ -6909,7 +6909,7 @@ rs6000_expand_vector_init (rtx target, rtx vals)
for (i = 0; i < n_elts; i++)
{
vr_qi[i] = gen_reg_rtx (V16QImode);
if (TARGET_64BIT)
if (TARGET_POWERPC64)
emit_insn (gen_p8_mtvsrd_v16qidi2 (vr_qi[i], op[i]));
else
emit_insn (gen_p8_mtvsrwz_v16qisi2 (vr_qi[i], op[i]));