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: Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr, kenner at vlsi1 dot ultra dot nyu dot edu
- Subject: Re: Beyond GCC 3.0: Summing Up
- From: dewar at gnat dot com
- Date: Tue, 10 Jul 2001 08:10:47 -0400 (EDT)
- Cc: gcc at gcc dot gnu dot org
<<But how is this process going to be "managed" any better than getting the
latent bug fixed with the patch *in* the tree? What's going to prevent the
"temporarily" from becoming indefinite?
>>
Better that the new incorrect/incomplete patch stay out indefinitely than
that the compiler stay significantly broken indefinitely! Of course the
"significantly" here is an important qualifier, see my previous messages.
<<Right, but the situation we're talking about here is not a major breakage
of that scale, but merely some regression test failures on some targets.
>>
I know that Richard tends not to regard "merely some regressoin test failures
on some targets" as serious, but in fact such test failures may represent
very serious problems that simply must be addressed urgently.