Vlad's recent IRA changes twiddled register allocation slightly causing some
tests to regress. See
http://gcc.gnu.org/jenkins
And look at the failures in the last 24hrs.
Anyway, I'm working through them right now. This is the first issue.
xstormy16 fails one test because of the register allocation difference. I've
looked at the before/after and they appear equivalent in terms of code size and
likely performance. So I'm just updating the test.
Given these tests are scanning for specific instruction sequences with
particular register numbers, I'm surprised have stable they've been over time.
Anyway, I'm committing this to the trunk momentarily and will start a fresh
xstormy16 build.
Jeff
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index ff1d1da3300..0ea4ffcc5f9 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2020-02-29 Jeff Law <l...@redhat.com>
+
+ * gcc.target/xstormy16/sfr/06_sfrw_to_var.c: Update expected output.
+
2020-02-28 Iain Sandoe <i...@sandoe.co.uk>
* g++.dg/coroutines/torture/func-params-08.C: Update
diff --git a/gcc/testsuite/gcc.target/xstormy16/sfr/06_sfrw_to_var.c b/gcc/testsuite/gcc.target/xstormy16/sfr/06_sfrw_to_var.c
index 39cbab5c3e9..54c9baf8746 100644
--- a/gcc/testsuite/gcc.target/xstormy16/sfr/06_sfrw_to_var.c
+++ b/gcc/testsuite/gcc.target/xstormy16/sfr/06_sfrw_to_var.c
@@ -1,5 +1,5 @@
/* { dg-options { -nostartfiles below100.o -Tbelow100.ld -O2 } } */
-/* { dg-final { scan-assembler "mov.w r6,32532" } } */
+/* { dg-final { scan-assembler "mov.w r1,32532" } } */
#define SFR (*((volatile unsigned short*)0x7f14))
unsigned short *p = (unsigned short *) 0x7f14;
