From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Geert Bosch <bosch@gnat.com>
Cc: Zack Weinberg <zack@codesourcery.com>, <guerby@acm.org>,
<gcc@gcc.gnu.org>
Subject: Re: ACATS legal status cleared by FSF
Date: Thu, 06 Dec 2001 14:32:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0112062215490.19761-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <4DC29618-EA96-11D5-8627-00039344BF4A@gnat.com>
On Thu, 6 Dec 2001, Geert Bosch wrote:
> It is virtually impossible for people to "break" these tests, which
> is why I say they are of no value. Even if people *do* manage to break
> them (in the hypothetical case that the maintainers would not catch the
> error before approving), this will not go unnoticed for a long
> time anyway. In the mean time, the *only* programs affected are
> programs with fatal errors to start with.
I have not examined these tests, but for C I would consider it valuable
for every constraint from either standard version, and every diagnostic
message that the front end can issue, to have at least one test. (Ideally
the test suite should aim for high code coverage in the compiler; I
haven't tried running in conjunction with gcov to see how far away from
this we are.) In general I consider a patch which adds a diagnostic
without including a test exercising that code path, or adds a language
feature without proper tests for the associated constraints, to be
defective. I get the impression from this discussion that these tests
represent something similar for Ada - tests of the ways in which code can
be defective and diagnostics issued for it - and so would be of similar
value. It is just as much a fundamental part of avoiding regressions that
bad code remains diagnosed and the messages do not get worse, as that good
code continues to compile and code quality does not get worse.
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-12-06 22:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-12-06 15:10 ` Zack Weinberg
2001-12-06 15:41 ` Geert Bosch
2001-12-06 18:22 ` Zack Weinberg
2001-12-05 15:28 Richard Kenner
2001-12-05 15:41 ` guerby
2001-12-05 23:36 dewar
2001-12-06 15:01 Richard Kenner
2001-12-06 15:40 Richard Kenner
2001-12-06 17:38 dewar
2001-12-06 19:09 dewar
2001-12-07 3:18 Richard Kenner
2001-12-07 17:59 dewar
2001-12-07 18:50 mike stump
2001-12-07 18:57 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-09 14:00 dewar
2001-12-09 15:06 dewar
2001-12-09 15:55 ` Joseph S. Myers
2001-12-09 19:03 dewar
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=Pine.LNX.4.33.0112062215490.19761-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.org \
--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).