diff mbox series

[committed,RISC-V] Fix risc-v expected test output after recent iv changes

Message ID 339d2c5e-8266-46eb-ade0-a58708c4b739@gmail.com
State Committed
Commit 33e610110c933b0d65aa82d67864bb881768609f
Headers
Series [committed,RISC-V] Fix risc-v expected test output after recent iv changes |

Checks

Context Check Description
rivoscibot/toolchain-ci-rivos-lint success Lint passed
rivoscibot/toolchain-ci-rivos-apply-patch success Patch applied
rivoscibot/toolchain-ci-rivos-build--newlib-rv64gcv-lp64d-multilib success Build passed
rivoscibot/toolchain-ci-rivos-build--linux-rv64gc_zba_zbb_zbc_zbs-lp64d-multilib success Build passed
rivoscibot/toolchain-ci-rivos-build--linux-rv64gcv-lp64d-multilib success Build passed
linaro-tcwg-bot/tcwg_gcc_build--master-arm fail Patch failed to apply
rivoscibot/toolchain-ci-rivos-test success Testing passed
linaro-tcwg-bot/tcwg_gcc_build--master-aarch64 fail Patch failed to apply
linaro-tcwg-bot/tcwg_simplebootstrap_build--master-aarch64-bootstrap fail Patch failed to apply
linaro-tcwg-bot/tcwg_simplebootstrap_build--master-arm-bootstrap fail Patch failed to apply

Commit Message

Jeff Law Feb. 6, 2025, 7:39 p.m. UTC 
  Richard S's recent change to iv increment insertion removed a reg->reg 
move (which was its intent AFAICT).  This triggered a failure on a riscv 
test.

That test was meant to verify that we didn't have an extraneous reg->reg 
move due to a buglet in the risc-v splitters.  Before the 2023 change we 
had two vector reg->reg moves and after the 2023 fix we had just one. 
With Richard's change we have none ;-)  Adjusting test accordingly.

Pushed to the trunk.

Jeff
commit 33e610110c933b0d65aa82d67864bb881768609f
Author: Jeff Law <jlaw@ventanamicro.com>
Date:   Thu Feb 6 12:37:11 2025 -0700

    [RISC-V] Fix risc-v expected test output after recent iv changes
    
    Richard S's recent change to iv increment insertion removed a reg->reg move
    (which was its intent AFAICT).  This triggered a failure on a riscv test.
    
    That test was meant to verify that we didn't have an extraneous reg->reg move
    due to a buglet in the risc-v splitters.  Before the 2023 change we had two
    vector reg->reg moves and after the 2023 fix we had just one.  With Richard's
    change we have none ;-)  Adjusting test accordingly.
    
    Pushed to the trunk.
    
    gcc/testsuite
            * gcc.target/riscv/rvv/autovec/madd-split2-1.c: Update expected
            output.
diff mbox series

Patch

diff --git a/gcc/testsuite/gcc.target/riscv/rvv/autovec/madd-split2-1.c b/gcc/testsuite/gcc.target/riscv/rvv/autovec/madd-split2-1.c
index 4f99a5f87c4..8cc0c9f407c 100644
--- a/gcc/testsuite/gcc.target/riscv/rvv/autovec/madd-split2-1.c
+++ b/gcc/testsuite/gcc.target/riscv/rvv/autovec/madd-split2-1.c
@@ -10,4 +10,4 @@  foo (long *__restrict a, long *__restrict b, long n)
   return a[1];
 }
 
-/* { dg-final { scan-assembler-times {\tvmv1r\.v} 1 } } */
+/* { dg-final { scan-assembler-not {\tvmv1r\.v} } } */