From: mike stump <mrs@windriver.com>
To: dewar@gnat.com, kenner@vlsi1.ultra.nyu.edu, zack@codesourcery.com
Cc: gcc@gcc.gnu.org
Subject: Re: ACATS legal status cleared by FSF
Date: Fri, 07 Dec 2001 18:50:00 -0000 [thread overview]
Message-ID: <200112080236.SAA14563@kankakee.wrs.com> (raw)
> From: dewar@gnat.com
> To: kenner@vlsi1.ultra.nyu.edu, zack@codesourcery.com
> Cc: gcc@gcc.gnu.org
> Date: Fri, 7 Dec 2001 20:39:54 -0500 (EST)
> <<One possibility is to run the B tests in a non-conventional way, where all
> the test harness does is to check for the presence of at least one
> error line for each line marked ERROR. I don't know how hard such a
> harness is to write, and that's not the way B tests are usually done, but
> might work.
> >>
> That's not good enough, the errors often do not occur on exactly the correct
> lines.
We have years of experience with such a scheme for C++, it works, it
is useful, it isn't a maintenance burden. I find the value of it
easily outweighs the maintenance cost of it.
If your compiler randomly changes around where messages come out all
the time, maybe you should re-engineer it from the top down, fix all
of them to be correct, once, fix the testcases in the testsuite to
conform to it, and then refuse any changes to this status quo for 5-10
years, and then after 5 years, put in all the changes enmass you would
like, redo the testsuite, lather, rise, repeat.
next reply other threads:[~2001-12-08 2:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 18:50 mike stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-09 19:03 dewar
2001-12-09 15:06 dewar
2001-12-09 15:55 ` Joseph S. Myers
2001-12-09 14:00 dewar
2001-12-07 19:12 dewar
2001-12-09 13:02 ` Zack Weinberg
2001-12-09 14:52 ` guerby
2001-12-09 19:47 ` Geert Bosch
2001-12-07 18:57 dewar
2001-12-07 17:59 dewar
2001-12-07 3:18 Richard Kenner
2001-12-06 19:09 dewar
2001-12-06 17:38 dewar
2001-12-06 15:40 Richard Kenner
2001-12-06 15:01 Richard Kenner
2001-12-05 23:36 dewar
2001-12-05 15:28 Richard Kenner
2001-12-05 15:41 ` guerby
2001-12-05 15:13 guerby
2001-12-05 16:21 ` Joseph S. Myers
2001-12-05 18:00 ` Jerry van Dijk
2001-12-06 3:36 ` Geoff Keating
2001-12-06 9:34 ` Geert Bosch
2001-12-06 11:48 ` Zack Weinberg
2001-12-06 14:24 ` Geert Bosch
2001-12-06 14:32 ` Joseph S. Myers
2001-12-06 15:10 ` Zack Weinberg
2001-12-06 15:41 ` Geert Bosch
2001-12-06 18:22 ` Zack Weinberg
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=200112080236.SAA14563@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=zack@codesourcery.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).