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: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Subject: Re: Beyond GCC 3.0: Summing Up
- From: "H . J . Lu" <hjl at lucon dot org>
- Date: Tue, 10 Jul 2001 10:00:49 -0700
- Cc: gcc at gcc dot gnu dot org
- References: <10107101657.AA12720@vlsi1.ultra.nyu.edu>
On Tue, Jul 10, 2001 at 12:57:31PM -0400, Richard Kenner wrote:
> I am not sure if they want to put resources in testing every gcc to be
> released.
>
> Right. This is precisely why it is good to limit the release rate
> because, as you say, testing is extremely expensive.
There is a difference. I am suggesting make more bug fix releases so
that a Linux/xxxBSD distribution can build the whole distribution
with the current major release within a build cycle using a new gcc,
which may take weeks or months. Within that cycle, they are testing
a major gcc release, which consists of the .0 release and consequent
.0.x releases. Their goal is to find a reliable .0.x release which
can build the whole distribution. If the current release doesn't work
and takes too long for the next .0.x release, I don't they will even
try the new gcc.
H.J.