diff options
author | Richard Sandiford <richard.sandiford@linaro.org> | 2017-11-07 16:08:47 +0000 |
---|---|---|
committer | Richard Sandiford <rsandifo@gcc.gnu.org> | 2017-11-07 16:08:47 +0000 |
commit | f32c3adb8d77c0ebee112ecf26ae249c8574970e (patch) | |
tree | 5f2c9635d4a53a4d6b1b5fb91ec16b1e94e1d25d /gcc/gimplify.c | |
parent | 56ccfbd6085be730876ebab31f865e4499b27067 (diff) | |
download | gcc-f32c3adb8d77c0ebee112ecf26ae249c8574970e.zip gcc-f32c3adb8d77c0ebee112ecf26ae249c8574970e.tar.gz gcc-f32c3adb8d77c0ebee112ecf26ae249c8574970e.tar.bz2 |
[AArch64] Use aarch64_reg_or_imm instead of nonmemory_operand
Some of the shift expanders accepted nonmemory_operands but were only
able to handle register_operands or CONST_INTs. This is probably
academic without SVE, since we're not likely to see shifts by other
types of constant (const_wide_ints, consts, etc). But for SVE,
it's possible for a vectorised shift induction to have a CONST_POLY_INT
shift amount.
This patch makes the expanders use aarch64_reg_or_imm instead.
2017-11-07 Richard Sandiford <richard.sandiford@linaro.org>
gcc/
* config/aarch64/aarch64.md (ashl<mode>3, ashr<mode>3, lshr<mode>3)
(rotr<mode>3, rotl<mode>3): Use aarch64_reg_or_imm instead of
nonmmory_operand.
From-SVN: r254499
Diffstat (limited to 'gcc/gimplify.c')
0 files changed, 0 insertions, 0 deletions