| commit | 485a0ae0982abe8ccebdfd660aa45823a572714d | |
| author | Richard Earnshaw <rearnsha@arm.com> | |
| Wed, 11 May 2022 10:40:42 +0000 (11 11:40 +0100) | ||
| committer | Richard Earnshaw <rearnsha@arm.com> | |
| Fri, 13 May 2022 10:24:11 +0000 (13 11:24 +0100) | ||
| tree | d765cc8e012c6c03147e39fa1ed9350c0ae4ad3c | treesnapshot (tar.gz zip) |
| parent | 112447f8564c0307c5da99a4094a3a99f204239f | commitdiff |
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.
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.
| gcc/config/arm/arm.cc | diffblobblamehistory |