From: Diego Novillo <dnovillo@google.com>
To: gcc-patches@gcc.gnu.org
Subject: [tuples] Fix expected dejagnu patterns in constructors.c
Date: Tue, 24 Jul 2007 18:40:00 -0000 [thread overview]
Message-ID: <46A6454C.90503@google.com> (raw)
Chris was getting intermittent failures on this testcase because dejagnu was not matching the '[]' properly. Fixed by escaping the brace the required 1 million times.
2007-07-24 Diego Novillo <dnovillo@google.com>
* gcc.dg/gimple/constructors.c: Fix expected pattern.
Index: gcc.dg/gimple/constructors.c
===================================================================
--- gcc.dg/gimple/constructors.c (revision 126872)
+++ gcc.dg/gimple/constructors.c (working copy)
@@ -10,10 +10,10 @@ void foo()
bar(a);
}
-/* { dg-final { scan-tree-dump-times "gimpleir: a.0. = 1" 1 "gimple"} } */
-/* { dg-final { scan-tree-dump-times "gimpleir: a.1. = 2" 1 "gimple"} } */
-/* { dg-final { scan-tree-dump-times "gimpleir: a.2. = 3" 1 "gimple"} } */
-/* { dg-final { scan-tree-dump-times "gimpleir: a.3. = 4" 1 "gimple"} } */
-/* { dg-final { scan-tree-dump-times "gimpleir: a.4. = 5" 1 "gimple"} } */
+/* { dg-final { scan-tree-dump-times "gimpleir: a\\\[0\\\] = 1" 1 "gimple"} } *
+/* { dg-final { scan-tree-dump-times "gimpleir: a\\\[1\\\] = 2" 1 "gimple"} } *
+/* { dg-final { scan-tree-dump-times "gimpleir: a\\\[2\\\] = 3" 1 "gimple"} } *
+/* { dg-final { scan-tree-dump-times "gimpleir: a\\\[3\\\] = 4" 1 "gimple"} } *
+/* { dg-final { scan-tree-dump-times "gimpleir: a\\\[4\\\] = 5" 1 "gimple"} } *
/* { dg-final { scan-tree-dump-times "gimpleir: bar \\(&a\\)" 1 "gimple"} } */
/* { dg-final { cleanup-tree-dump "gimple" } } */
reply other threads:[~2007-07-24 18:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A6454C.90503@google.com \
--to=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).