This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.3 Branch
- From: Jan Hubicka <jh at suse dot cz>
- To: Bosscher Steven Civ USAFA/DFAN <Steven dot Bosscher at usafa dot af dot mil>
- Cc: 'Jan Hubicka' <jh at suse dot cz>,'Mark Mitchell' <mark at codesourcery dot com>,"'gcc at gcc dot gnu dot org'" <gcc at gcc dot gnu dot org>
- Date: Sat, 14 Dec 2002 11:55:47 +0100
- Subject: Re: GCC 3.3 Branch
- References: <15A5B6227F19D311856E00902746453504EE5DA1@fsxqpz05.usafa.af.mil>
> Jan Hubicka wrote:
> >
> > > We've fixed quite a few bugs on the mainline, but obviously there are
> > > a lot to go before GCC 3.3 is ready. Still, we may as well allow
> > > people to start pushing things to the new mainline for GCC 3.4. (I'll
> >
> > Great, that gives chance to finish the merge of cfg branch now prepared
> > on rtlopt branch. I will try to push the remaining bits present on
> > cfg branch only into mergeable shape soon. I expect I can take a week
> > or so as there will be enough to merge in meantime :)
>
> With so many branches ready to merge, would it be an idea to first merge the
> rtlopt and cp-parser into the basic_improvement branch and make sure that it
> bootstraps and doesn't cause (too m)any regressions?
That may result in breaking BIB branch so we won't be able to merge
anything. I would preffer to merge things incrementally. For rtlopt
branch I plan to split it into series of patches as we did for cfg
branch last time. That way the individual patches can be better
rewieved and verified, but it will take at lest month or so to finish
the merge I would expect.
I am keeping rtlopt branch in sync with BIB branch, so testing can
simply happen there. I plan to test the architectures I have
accessible (i386, x86-64, mips, sparc, alpha, PPC) as well as build some
software packages with it, so hope it will get enought of testing.
Honza
>
> Greetz
> Steven