]> git.ipfire.org Git - thirdparty/gcc.git/commit
[to-be-committed][RISC-V][PR target/115142] Do not create invalidate shift-add insn
authorJeff Law <jlaw@ventanamicro.com>
Sun, 19 May 2024 15:56:16 +0000 (09:56 -0600)
committerJeff Law <jlaw@ventanamicro.com>
Sun, 19 May 2024 15:56:16 +0000 (09:56 -0600)
commite1ce9c37ed68136a99d44c8301990c184ba41849
tree50edb12b0b480d6a04d54582adca82061b7954c4
parent1073469074ff132478ec8d923ed8635c672f7d9b
[to-be-committed][RISC-V][PR target/115142] Do not create invalidate shift-add insn

The circumstances which triggered this weren't something that should appear in
the wild (-ftree-ter, without optimization enabled).  So I wasn't planning to
backport.  Obviously if it shows up in another context we can revisit that
decision.

I've run this through my rv32gcv and rv64gc tester.  Waiting on the CI system before committing.

PR target/115142
gcc/

* config/riscv/riscv.cc (mem_shadd_or_shadd_rtx_p): Make sure
shifted argument is a register.

gcc/testsuite

* gcc.target/riscv/pr115142.c: New test.
gcc/config/riscv/riscv.cc
gcc/testsuite/gcc.target/riscv/pr115142.c [new file with mode: 0644]