This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Beyond GCC 3.0: Summing Up
- To: bernds at redhat dot com, dewar at gnat dot com
- Subject: Re: Beyond GCC 3.0: Summing Up
- From: dewar at gnat dot com
- Date: Tue, 10 Jul 2001 13:43:59 -0400 (EDT)
- Cc: gcc at gcc dot gnu dot org, kenner at vlsi1 dot ultra dot nyu dot edu
>>Did others agree with that analysis?
Usually no .. no one knew enough to be sure ... and our viewpoint is that
it does not really matter that much, what matters is whether the resulting
version is broken.
Of course the best thing in cases where there is a latent bug exposed is
to try to figure out a test case which exposes the latest bug without
needing the new patch that breaks things. This is often possible once
you have things figured out, and in that case this new case can be added
to the test suite, and you have a sharp bug to focus on without needing
to break the top of tree