Branching for GCC 3.0

[Mark Mitchell]

Richard's patch to support -shared-libgcc was the last functional item
on my list of things to do before GCC 3.0.

(I know that there are still some V3 issues on AIX, and HPUX.  These
need to get resolved before the release, but not necessarily before we
branch.  However, I would like to see these resolved ASAP.  This has
dragged on too long.  Benjamin, do you have access to an AIX box?  If
so, would you mind taking a look at what is going wrong at
initialization-time?)

(I also know that Jason and Richard are interested in incorporating
the high-level bits of the IA64 exception API into GCC.  I fully
support this effort -- but I think I would prefer not to hold up 3.0
for that work.  However, if Jason/Richard have a short-term time frame
for this work, it might make sense to incorporate it.)

Since there is definitely a trend towards major movement on the
mainline, I think it is appropriate to branch for GCC 3.0 sooner,
rather than later.  Many bug-fix patches will need to go on both
branches, but all new functionality can go on the mainline, and help
us keep the release branch stable.

I propose that we branch next weekend, on January 14th, assuming we're
getting successful bootstraps on some major platforms at that point.

As a baseball coach of mine used to say:

  Questions, comments, theories, or philosophies?

Thanks,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com