public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r13-416] arm: fix some issues in mve_vector_mem_operand
@ 2022-05-13 10:25 Richard Earnshaw
0 siblings, 0 replies; only message in thread
From: Richard Earnshaw @ 2022-05-13 10:25 UTC (permalink / raw)
To: gcc-cvs
https://gcc.gnu.org/g:485a0ae0982abe8ccebdfd660aa45823a572714d
commit r13-416-g485a0ae0982abe8ccebdfd660aa45823a572714d
Author: Richard Earnshaw <rearnsha@arm.com>
Date: Wed May 11 11:40:42 2022 +0100
arm: fix some issues in mve_vector_mem_operand
There are a couple of issues with the mve_vector_mem_operand function.
Firstly, SP is permitted as a register provided there is no write-back
operation. Secondly, there were some cases where 'strict' was not
being applied when checking which registers had been used.
gcc/ChangeLog:
* config/arm/arm.cc (mve_vector_mem_operand): Allow SP_REGNUM
when there is no write-back. Fix use when strict is true.
Diff:
---
gcc/config/arm/arm.cc | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/gcc/config/arm/arm.cc b/gcc/config/arm/arm.cc
index 69a18c2f157..2afe0445ed5 100644
--- a/gcc/config/arm/arm.cc
+++ b/gcc/config/arm/arm.cc
@@ -13527,7 +13527,7 @@ mve_vector_mem_operand (machine_mode mode, rtx op, bool strict)
int reg_no = REGNO (op);
return (((mode == E_V8QImode || mode == E_V4QImode || mode == E_V4HImode)
? reg_no <= LAST_LO_REGNUM
- :(reg_no < LAST_ARM_REGNUM && reg_no != SP_REGNUM))
+ : reg_no < LAST_ARM_REGNUM)
|| (!strict && reg_no >= FIRST_PSEUDO_REGISTER));
}
code = GET_CODE (op);
@@ -13536,10 +13536,10 @@ mve_vector_mem_operand (machine_mode mode, rtx op, bool strict)
|| code == PRE_INC || code == POST_DEC)
{
reg_no = REGNO (XEXP (op, 0));
- return ((mode == E_V8QImode || mode == E_V4QImode || mode == E_V4HImode)
- ? reg_no <= LAST_LO_REGNUM
- :(reg_no < LAST_ARM_REGNUM && reg_no != SP_REGNUM))
- || reg_no >= FIRST_PSEUDO_REGISTER;
+ return (((mode == E_V8QImode || mode == E_V4QImode || mode == E_V4HImode)
+ ? reg_no <= LAST_LO_REGNUM
+ :(reg_no < LAST_ARM_REGNUM && reg_no != SP_REGNUM))
+ || (!strict && reg_no >= FIRST_PSEUDO_REGISTER));
}
else if (((code == POST_MODIFY || code == PRE_MODIFY)
&& GET_CODE (XEXP (op, 1)) == PLUS
@@ -13580,10 +13580,11 @@ mve_vector_mem_operand (machine_mode mode, rtx op, bool strict)
default:
return FALSE;
}
- return reg_no >= FIRST_PSEUDO_REGISTER
- || (MVE_STN_LDW_MODE (mode)
- ? reg_no <= LAST_LO_REGNUM
- : (reg_no < LAST_ARM_REGNUM && reg_no != SP_REGNUM));
+ return ((!strict && reg_no >= FIRST_PSEUDO_REGISTER)
+ || (MVE_STN_LDW_MODE (mode)
+ ? reg_no <= LAST_LO_REGNUM
+ : (reg_no < LAST_ARM_REGNUM
+ && (code == PLUS || reg_no != SP_REGNUM))));
}
return FALSE;
}
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-05-13 10:25 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-13 10:25 [gcc r13-416] arm: fix some issues in mve_vector_mem_operand Richard Earnshaw
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).