Hello,
This:
http://gcc.gnu.org/ml/gcc-patches/2013-06/msg00767.html
recently introduced test case uses the pattern:
/* { dg-final { scan-rtl-dump-not "REG_EQUIV.*mem.*\"ip\"" "ira" } } */
I believe the intention is to look for the three tokens, in order within
a single instruction, the actual effect is to look for the three tokens,
in order, anywhere in the dump file. The test fails for at least arm-*
and aarch64-* where we happen to have the appropriate three tokens
spread through the dump file.
/Marcus
2013-07-04 Marcus Shawcroft <marcus.shawcr...@arm.com>
* gcc.dg/pr57518.c: Adjust scan-rtl-dump-not pattern.diff --git a/gcc/testsuite/gcc.dg/pr57518.c b/gcc/testsuite/gcc.dg/pr57518.c
index 4c84a85..47e819c 100644
--- a/gcc/testsuite/gcc.dg/pr57518.c
+++ b/gcc/testsuite/gcc.dg/pr57518.c
@@ -2,7 +2,7 @@
/* { dg-do compile } */
/* { dg-options "-O2 -fdump-rtl-ira" } */
-/* { dg-final { scan-rtl-dump-not "REG_EQUIV.*mem.*\"ip\"" "ira" } } */
+/* { dg-final { scan-rtl-dump-not "REG_EQUIV\[^\n\]*mem\[^\n\]*\"ip\"" "ira" } } */
char ip[10];
int total;
