More minor fallout from Vlad's IRA changes.

Previously this test used r3 to hold a value across a call (it's an ipa-ra
test).  After Vlad's changes we're using r1 instead.

This patch makes the obvious change to pattern we can for which should bring
the test back to a passing status.

There's a note about r3 being special on thumb1 and the pattern check is
skipped for thumb1.  That special casing my not be necessary anymore -- I leave
that to the ARM maintainers to resolve one way or the other.

Committing on the trunk momentarily.

jeff
commit 0ce38183001095c804b45bab0370ff50b34f886f
Author: Jeff Law <l...@redhat.com>
Date:   Mon Mar 2 08:44:28 2020 -0700

    Fix testsuite regression due to recent IRA changes.
    
            * gcc.target/arm/fuse-caller-save.c: Update expected output.

diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 988d49af3b8..3f2c2851799 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2020-03-02  Jeff Law  <l...@redhat.com>
+
+       * gcc.target/arm/fuse-caller-save.c: Update expected output.
+
 2020-03-02  Martin Liska  <mli...@suse.cz>
 
        * gcc.dg/vect/bb-slp-19.c: The comment
diff --git a/gcc/testsuite/gcc.target/arm/fuse-caller-save.c 
b/gcc/testsuite/gcc.target/arm/fuse-caller-save.c
index ef9256dced9..20837125c0a 100644
--- a/gcc/testsuite/gcc.target/arm/fuse-caller-save.c
+++ b/gcc/testsuite/gcc.target/arm/fuse-caller-save.c
@@ -22,4 +22,4 @@ main (void)
 
 /* For thumb1, r3 is considered likely spilled, and treated differently in
    ira_build_conflicts, which inhibits the fipa-ra optimization.  */
-/* { dg-final { scan-assembler-times "mov\tr3, r0" 1 { target { ! arm_thumb1 } 
} } } */
+/* { dg-final { scan-assembler-times "mov\tr1, r0" 1 { target { ! arm_thumb1 } 
} } } */

Reply via email to