This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Testsuite policy - test case now passes but bug remains
- To: David dot Billinghurst at riotinto dot com dot au
- Subject: Re: Testsuite policy - test case now passes but bug remains
- From: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
- Date: Sun, 18 Jun 2000 18:42:42 +0200
- CC: mark at codesourcery dot com, gcc at gcc dot gnu dot org
- References: <A9E96A79C068D211A6A90000C07BDF0D4D4DA8@crtsmail.crts.techaust.riotinto.com.au>
> I'm pretty certain that the original bug is still there, as the failure is
> the same. It's just that it is no longer triggered in the original reduced
> testcase. Trivial and apparently unrelated changes to the testcase
> retrigger the problem - essentially declaring another unused array in the
> subroutine.
One thing that hasn't been mentioned: The testsuite is *not* a place
to keep track of bug reports - GNATS is the place for that.
So I think new test cases should *only* be added when a bug had been
fixed (or, at the discretion of maintainers, for any other reason they
please), to make sure that the same bug does not re-occur. Adding a
test case on its own (i.e. without knowing the fix for the testcase)
is pointless, IMO.
Regards,
Martin