From: David Carlton <carlton@kealia.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
jimb@redhat.com, fnasser@redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: RFA: Don't include value of expression in pc-fp.exp test name
Date: Wed, 01 Oct 2003 19:33:00 -0000 [thread overview]
Message-ID: <yf2oex0kb2p.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <3F7B1D16.4010009@redhat.com> (Andrew Cagney's message of "Wed, 01 Oct 2003 14:29:42 -0400")
On Wed, 01 Oct 2003 14:29:42 -0400, Andrew Cagney <ac131313@redhat.com> said:
> To split hairs, I can see two cases:
> - two runs within identical environments
> I can see 'diff -u' reasonably working here.
> - two runs within different environments
> After paren stripping the results should be identical (or close two it).
> For instance sizeof.exp contains various tests to check that sizes
> are sane. The actual sizes found are included in the output.
> That's fine since if the numbers were to change between runs the
> test results are pretty sunk.
That's a very good point. I've seen variants of this myself: I've
seen interesting differences between test runs if I change GCC
versions/debug formats, as well. For example, this can show up in
tests with multiple PASS branches: sometimes, it can be interesting to
know which PASS branch you hit (or, rather, if you had a change from
one PASS branch to another PASS branch), so putting information in
parentheses there is useful.
I would be quite happy if we adopted the philosophy that the only
stuff that you should put in parentheses satisfies these conditions:
* It shouldn't change if the environment changes (for some appropriate
value of "the environment changes").
* If it does change while the enviroment stays the same, then you want
to know about it.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-10-01 19:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 16:44 Michael Elizabeth Chastain
2003-10-01 18:29 ` Andrew Cagney
2003-10-01 19:33 ` David Carlton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-02 22:43 Michael Elizabeth Chastain
2003-10-01 19:06 Michael Elizabeth Chastain
2003-10-02 21:55 ` Andrew Cagney
2003-10-01 4:12 Michael Elizabeth Chastain
2003-09-30 17:49 Michael Elizabeth Chastain
2003-09-30 22:18 ` Jim Blandy
2003-10-01 15:31 ` Andrew Cagney
2003-10-01 15:49 ` David Carlton
[not found] <200309291917.h8TJHLhn010447@duracef.shout.net>
2003-09-30 6:44 ` Jim Blandy
2003-09-30 15:36 ` David Carlton
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=yf2oex0kb2p.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=ac131313@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=mec@shout.net \
/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