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: Jan Hubicka <jh at suse dot cz>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Benjamin Kosnik <bkoz at redhat dot com>,Matt Austern <austern at apple dot com>,"jsm28 at cam dot ac dot uk" <jsm28 at cam dot ac dot uk>,"gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sat, 1 Feb 2003 02:43:31 +0100
- Subject: Re: GCC 3.3, GCC 3.4
- References: <20030131165429.32d4d907.bkoz@redhat.com> <57100000.1044062940@warlock.codesourcery.com>
>
>
> --On Friday, January 31, 2003 04:54:29 PM -0600 Benjamin Kosnik
> <bkoz@redhat.com> wrote:
>
> >
> >Agreed. Seems to be a common concern.
> >
> >Mark, I think keeping at least a month in between the two events is
> >advisable.
>
> That actually is our normal plan.
>
> But it's a bit hard to have it both ways -- if we can't commit to a
> 3.3 date (as you suggested yesterday that we should not) then we can't
> really schedule the 3.4 cutoff.
>
> But, we have been in 3.4 stage one for quite some time now, and Geoff
> and I both managed to get our work ready at that time. Stage 1 isn't
> really for *developing* new major changes, it's for *integrating* them.
We would like to integrate the rtlopt branch as well. The changes are
already developed for quite some time, so I believe they are ready for
being added into mainline now. Hope it will fir the schedule.
Honza
>
> We could just close the mainline during a release, but it's very clear
> that nobody wants to do that -- we want to make sure development can
> happen while a release is being prepared. That inherently means that
> there's going to be some division of people's time between the two
> branches.
>
> --
> Mark Mitchell mark@codesourcery.com
> CodeSourcery, LLC http://www.codesourcery.com