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: dewar at gnat dot com
- Subject: Re: Beyond GCC 3.0: Summing Up
- From: "H . J . Lu" <hjl at lucon dot org>
- Date: Tue, 10 Jul 2001 09:08:11 -0700
- Cc: mark at codesourcery dot com, aoliva at redhat dot com, gcc at gcc dot gnu dot org,kenner at vlsi1 dot ultra dot nyu dot edu
- References: <20010710112256.6EE8CF2B12@nile.gnat.com>
On Tue, Jul 10, 2001 at 07:22:56AM -0400, dewar@gnat.com wrote:
> <<You will set yourself up for a failure if you want to make a perfect
> release. To me, gcc 3.0 is a decent .0 release, which is buggy by
> default. I don't think an incremental bug fix gcc 3.0.x for every
> 2 or 3 weeks is a bad idea. I don't understand why anyone wants to
> fix all regressions in 3.0.1. I can tell you right now that you will
> >>
>
> I don't think it is practical to make incremental releases so rapidly,
> full qualification of a release is bound to take quite a bit of effort.
That is the problem. I agree we should have a full qualification for
a major relese, even that won't guarantee you a perfect release. We
are talking the bug fix release here. Presumably, changes are
relatively small. Shouldn't put our energy into getting more releases
out rather than making full qualifications? To me, making a bug fix
release itself is one kind of qualification. Many gcc bugs won't be
discovered until the users start using the new gcc. Why not let users
help us make a great gcc, which the gcc developers can't do by
ourselves alone anyway?
H.J.