From: Thomas Preud'homme <thomas.preudhomme@foss.arm.com>
To: gcc-patches@gcc.gnu.org, ro@cebitec.uni-bielefeld.de,
mikestump@comcast.net
Subject: [PATCH, testsuite] Stabilize test result output of dump-noaddr
Date: Tue, 12 Jan 2016 08:48:00 -0000 [thread overview]
Message-ID: <7361233.vHt7sE6BKY@hardin.shanghai.arm.com> (raw)
Hi,
Everytime the static pass number of passes change, testsuite output for dump-
noaddr will change, leading to a series of noise lines like the following
under dg-cmp-results:
PASS->NA: gcc.c-torture/unsorted/dump-noaddr.c.036t.fre1, -O1 comparison
PASS->NA: gcc.c-torture/unsorted/dump-noaddr.c.036t.fre1, -O2 comparison
PASS->NA: gcc.c-torture/unsorted/dump-noaddr.c.036t.fre1, -O2 -flto -fno-use-
linker-plugin -flto-partition=none comparison
PASS->NA: gcc.c-torture/unsorted/dump-noaddr.c.036t.fre1, -O2 -flto -fuse-
linker-plugin -fno-fat-lto-objects comparison
PASS->NA: gcc.c-torture/unsorted/dump-noaddr.c.036t.fre1, -O3 -fomit-frame-
pointer -funroll-loops -fpeel-loops -ftracer -finline-functions comparison
PASS->NA: gcc.c-torture/unsorted/dump-noaddr.c.036t.fre1, -O3 -g comparison
PASS->NA: gcc.c-torture/unsorted/dump-noaddr.c.036t.fre1, -Og -g comparison
PASS->NA: gcc.c-torture/unsorted/dump-noaddr.c.036t.fre1, -Os comparison
NA->PASS: gcc.c-torture/unsorted/dump-noaddr.c.034t.fre1, -O1 comparison
NA->PASS: gcc.c-torture/unsorted/dump-noaddr.c.034t.fre1, -O2 comparison
NA->PASS: gcc.c-torture/unsorted/dump-noaddr.c.034t.fre1, -O2 -flto -fno-use-
linker-plugin -flto-partition=none comparison
NA->PASS: gcc.c-torture/unsorted/dump-noaddr.c.034t.fre1, -O2 -flto -fuse-
linker-plugin -fno-fat-lto-objects comparison
NA->PASS: gcc.c-torture/unsorted/dump-noaddr.c.034t.fre1, -O3 -fomit-frame-
pointer -funroll-loops -fpeel-loops -ftracer -finline-functions comparison
NA->PASS: gcc.c-torture/unsorted/dump-noaddr.c.034t.fre1, -O3 -g comparison
NA->PASS: gcc.c-torture/unsorted/dump-noaddr.c.034t.fre1, -Og -g comparison
NA->PASS: gcc.c-torture/unsorted/dump-noaddr.c.034t.fre1, -Os comparison
This patch solve this problem by replacing the static pass number in the
output by a star, allowing for a stable output while retaining easy copy/
pasting in shell.
ChangeLog entry is as follows:
*** gcc/testsuite/ChangeLog ***
2015-12-30 Thomas Preud'homme <thomas.preudhomme@arm.com>
* gcc.c-torture/unsorted/dump-noaddr.x (dump_compare): Replace static
pass number in output by a star.
diff --git a/gcc/testsuite/gcc.c-torture/unsorted/dump-noaddr.x b/gcc/
testsuite/gcc.c-torture/unsorted/dump-noaddr.x
index a8174e0..001dd6b 100644
--- a/gcc/testsuite/gcc.c-torture/unsorted/dump-noaddr.x
+++ b/gcc/testsuite/gcc.c-torture/unsorted/dump-noaddr.x
@@ -18,6 +18,7 @@ proc dump_compare { src options } {
foreach dump1 [lsort [glob -nocomplain dump1/*]] {
regsub dump1/ $dump1 dump2/ dump2
set dumptail "gcc.c-torture/unsorted/[file tail $dump1]"
+ regsub {\.\d+((t|r|i)\.[^.]+)$} $dumptail {.*\1} dumptail
#puts "$option $dump1"
set tmp [ diff "$dump1" "$dump2" ]
if { $tmp == 0 } {
Is this ok for stage3?
Best regards,
Thomas
next reply other threads:[~2016-01-12 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 8:48 Thomas Preud'homme [this message]
2016-01-12 11:44 ` Mike Stump
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=7361233.vHt7sE6BKY@hardin.shanghai.arm.com \
--to=thomas.preudhomme@foss.arm.com \
--cc=gcc-patches@gcc.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).