This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC-4.0.4 release status
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>
- Cc: Gabriel Dos Reis <gdr at cs dot tamu dot edu>, gcc at gcc dot gnu dot org
- Date: Thu, 25 Jan 2007 11:20:31 -0800
- Subject: Re: GCC-4.0.4 release status
- References: <59025.83.236.132.10.1169743351.squirrel@www.igpm.rwth-aachen.de>
On Thu, Jan 25, 2007 at 05:42:31PM +0100, Volker Reichelt wrote:
> Hi,
>
> > There were over 250 PRs open against GCC-4.0.4. Almost all of
> > them are "benign" in the sense that we can leave without fixing them
> > in GCC-4.0.4 -- many are already fixed in more recent versions.
> > I'm now giving attention only to those PRs marked as blocker or
> > critical. I've identified three:
>
> Well, there's another serious (wrong-code) bug which should be fixed IMHO:
>
> PR c++/29106 is a C++ front-end issue.
> It has a one-line fix (plus comment) on the 4.1 branch.
> Well, actually one should also backport the fix for PR c++/28284 then,
> which is a two-liner.
>
> Unfortunately, I didn't find the time to test the patch myself.
The goal of 4.0.4 is to get out the code that is already in the 4.0 branch
and then shut it down, so we can then close about 150 "only in 4.0.x" bugs
and be done with it.
To me, the only strong criterion is that 4.0.4 should be strictly better
than 4.0.3; AFAIK none of the three bugs Gaby mentioned work in 4.0.3.
It might be worth fixing a couple of wrong-code bugs that are already
fixed in 4.1 and have very trivial fixes. I don't think it's wise,
though, to backport fixes from the 4.1 branch that are broken in 4.1.1
unless there's a really strong justification. We don't want to create
incentives to move backwards.