From: Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
To: gcc-patches@gnu.org
Cc: ro@cebitec.uni-bielefeld.de, mikestump@comcast.net
Subject: [PATCH/RFA] Fix up gcc.dg/vect/pr30858.c expected output
Date: Fri, 14 Oct 2011 15:12:00 -0000 [thread overview]
Message-ID: <4E984AA4.7050105@arm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
All,
The attached patch corrects the expected output of the
gcc.dg/vect/pr30858.c testcase.
Historically it has expected the output "Unknown def-use cycle pattern."
just once.
However, recent changes to GCC for ARM targets means that vectorization
is attempted twice once with a vector size of 128-bits and once with a
vector size of 64-bits. This means that the output appears more than once.
The patch works around this by making the testcase expect one or more
instances of "Unknown def-use cycle pattern"
Can someone review please?
Thanks,
Matt
gcc/testsuite/ChangeLog:
2011-10-13 Matthew Gretton-Dann <matthew.gretton-dann@arm.com>
* gcc.dg/vect/pr30858.c: Update expected output for
architectures with multiple vector sizes.
--
Matthew Gretton-Dann
Principal Engineer, PD Software - Tools, ARM Ltd
[-- Attachment #2: 1110-fix-pr30858.txt --]
[-- Type: text/plain, Size: 538 bytes --]
diff --git a/gcc/testsuite/gcc.dg/vect/pr30858.c b/gcc/testsuite/gcc.dg/vect/pr30858.c
index 0af2f8e..0e7f7e1 100644
--- a/gcc/testsuite/gcc.dg/vect/pr30858.c
+++ b/gcc/testsuite/gcc.dg/vect/pr30858.c
@@ -11,5 +11,5 @@ foo (int ko)
}
/* { dg-final { scan-tree-dump-times "vectorized 0 loops" 1 "vect" } } */
-/* { dg-final { scan-tree-dump-times "Unknown def-use cycle pattern." 1 "vect" } } */
+/* { dg-final { scan-tree-dump "Unknown def-use cycle pattern." "vect" } } */
/* { dg-final { cleanup-tree-dump "vect" } } */
next reply other threads:[~2011-10-14 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 15:12 Matthew Gretton-Dann [this message]
2011-10-16 10:05 ` Ira Rosen
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=4E984AA4.7050105@arm.com \
--to=matthew.gretton-dann@arm.com \
--cc=gcc-patches@gnu.org \
--cc=mikestump@comcast.net \
--cc=ro@cebitec.uni-bielefeld.de \
/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).