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: Mark Mitchell <mark at codesourcery dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: "tromey at redhat dot com" <tromey at redhat dot com>, "dje at watson dot ibm dot com" <dje at watson dot ibm dot com>, "jbuck at synopsys dot com" <jbuck at synopsys dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 03 Feb 2003 13:52:40 -0800
- Subject: Re: GCC 3.3, GCC 3.4
--On Monday, February 03, 2003 03:45:50 PM -0600 Benjamin Kosnik
<bkoz@redhat.com> wrote:
Right now, we have a window in which to merge branches. If you're
ready, you merge; if you're not, you don't. We successfuly merged
some major technology that way for 3.4.
I guess your definition of "ready to merge" is what I don't understand.
Could you please elaborate on it?
The PCH and parser branches caused no regressions in the testsuite, and,
in the opinion of people with approval authority, were in good shape.
They met the criteria of working on a variety of platforms.
I don't know of branches that are not in that shape, because I haven't
been involved with them. This is something where we have to trust the
branch maintainers, largely.
However, certainly the parser wasn't ready for the last release. For
example, there were still numerous test failures, it was very slow, and
there were pieces of C++ that weren't handled correctly.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com