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: "'Mark Mitchell'" <mark at codesourcery dot com>
- Subject: RE: Testsuite policy - test case now passes but bug remains
- From: "Billinghurst, David (CRTS)" <David dot Billinghurst at riotinto dot com dot au>
- Date: Fri, 16 Jun 2000 00:03:11 -0000
- Cc: gcc at gcc dot gnu dot org
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.
> -----Original Message-----
> From: Mark Mitchell [SMTP:mark@codesourcery.com]
> Sent: Friday, 16 June 2000 10:00
> To: Billinghurst, David (CRTS)
> Cc: gcc@gcc.gnu.org
> Subject: Re: Testsuite policy - test case now passes but bug remains
>
>
> A question about testsuite policy/etiquette?
>
> Recently I found a g77 bug, produced a simple testcase and submitted it
> to
> the g77 testsuite as 20000601-1.f
> http://gcc.gnu.org/ml/gcc-bugs/2000-05/msg01005.html . The problem
> seems
> restricted to mips-sgi-irix6.5 with -mabi=64. Now the testcase passes
> but
> the original bug remains.
>
> Should I:
>
> * submit a new testcase (probably not)
>
> Actually, that's the right answer. You submitted a test-case for a
> bug. That bug was fixed -- but some other bug is still there. Submit
> a second test-case for the second bug. Even if the causes are
> related, it's good to have lots of test coverage for the parts of the
> compiler that have historically been weak.
>
> --
> Mark Mitchell mark@codesourcery.com
> CodeSourcery, LLC http://www.codesourcery.com