This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.3, GCC 3.4
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- To: gcc at gcc dot gnu dot org
- Cc: Benjamin Kosnik <bkoz at redhat dot com>, Mark Mitchell <mark at codesourcery dot com>
- Date: Fri, 31 Jan 2003 01:40:56 +0100 (CET)
- Subject: Re: GCC 3.3, GCC 3.4
- References: <20030130181313.7d3c5820.bkoz@redhat.com>
On Thu, 30 Jan 2003, Benjamin Kosnik wrote:
> Shipping GCC 3.3.0 on March 1 will require enormous effort.
Agreed. What worries me more, though, is that currently we have
~59 high priority PRs = regressions for the 3.2-branch (most of
which also apply to 3.3).
I believe we should try to tackle these first (and deliver a
sensibly improved GCC 3.2.3 after the forthcoming 3.2.2).
>> There's more I'd like to say, but I can't. Hopefully soon.
> This continues to annoy me, but I understand why you do it. The longer
> you say this line, the less I believe there's anything to say.
Given how many ABI bugs CodeSourcery developers have already fixed
(and the fact that I cannot remember Mark ever promising something
he hasn't kept), I'm much more optimistic.
BTW, if you consider my finding of C ABI breakage for several, not so
minor platforms today, apparently we could also use a C ABI testsuite.
> I think the longer gcc, as a project, goes on without an autobuild
> continuous regression checker, the worse off things will get. Somebody
> [...] will have to step up with the bandwidth, time, and machine to do
> this.
Fully agreed.
Well, why don't we send a "Call for support" to the gcc-announce list?
Seriously.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/