From: James Lemke <jwlemke@wasabisystems.com>
To: Mike Stump <mrs@apple.com>
Cc: gcc@gcc.gnu.org
Subject: Re: comparing DejaGNU results
Date: Thu, 01 Jun 2006 20:26:00 -0000 [thread overview]
Message-ID: <1149193578.4755.75.camel@winch.thelemkes.ca> (raw)
In-Reply-To: <1149190523.4755.59.camel@winch.thelemkes.ca>
> Your approach is faster, esp. on Darwin / NetBSD.
> The only advantages I see to mine is handling variants (Richard's patch
> fixes that), verbosity control, and detail -- compare_tests only looks
> at X?(PASS|FAIL).
Hmm.. another small point, FWIW.
Both the results files I used contained the following ssequence of
results:
PASS: gcc.c-torture/compile/930210-1.c (test for excess errors)
PASS: gcc.c-torture/compile/930210-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/930210-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/930210-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/930210-1.c (test for excess errors)
PASS: gcc.c-torture/compile/930210-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/930210-1.c (test for excess errors)
FAIL: gcc.c-torture/compile/930210-1.c (test for excess errors)
compare_tests reported the following:
Tests that now fail, but worked before:
gcc.c-torture/compile/930210-1.c (test for excess errors)
gcc.c-torture/compile/930210-1.c (test for excess errors)
gcc.c-torture/compile/930210-1.c (test for excess errors)
:
Tests that now work, but didn't before:
gcc.c-torture/compile/930210-1.c (test for excess errors)
gcc.c-torture/compile/930210-1.c (test for excess errors)
gcc.c-torture/compile/930210-1.c (test for excess errors)
dg-cmp-results didn't report anything (at that verbosity) because
nothing had changed.
--
Jim Lemke jwlemke@wasabisystems.com Orillia, Ontario
next prev parent reply other threads:[~2006-06-01 20:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 18:13 James Lemke
2006-05-31 18:25 ` Joe Buck
2006-05-31 18:28 ` Jeffrey Law
2006-05-31 18:33 ` James Lemke
2006-05-31 18:45 ` Joe Buck
2006-06-01 0:56 ` Ben Elliston
2006-06-01 0:59 ` Andrew Pinski
2006-06-01 2:17 ` Mike Stump
2006-06-01 1:14 ` Jim Wilson
2006-06-01 2:43 ` Mike Stump
2006-06-01 8:46 ` Richard Earnshaw
2006-06-01 17:27 ` Mike Stump
2006-06-01 19:35 ` James Lemke
2006-06-01 20:26 ` James Lemke [this message]
2006-06-01 20:36 ` Joseph S. Myers
2006-06-01 20:42 ` James Lemke
2006-06-02 18:08 ` James Lemke
2006-06-02 23:27 ` Mike Stump
2006-06-03 12:35 ` James Lemke
2006-06-01 19:44 ` James Lemke
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=1149193578.4755.75.camel@winch.thelemkes.ca \
--to=jwlemke@wasabisystems.com \
--cc=gcc@gcc.gnu.org \
--cc=mrs@apple.com \
/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).