GCC 3.1 Release

[Mark Mitchell <mark@codesourcery.com>]

As should be clear at this point, there is no way that we are going
to be shipping GCC 3.1 on Monday.

The amount of breakage since GCC 3.0 continues to amaze me.

We still have about 30 open bugs that we need to try to resolve
for this release.

To that end, I'm as of now slipping the GCC 3.1 release date by two
weeks, until May 1st.

I have a proposal before the SC to slip the GCC 3.2 schedule even
further; so that the first phase of GCC 3.2 development will now end
one month  beyond the release of GCC 3.1 -- June 1st -- pushing the
GCC 3.2  release date back to October 1st so as to give people time to
work on major changes for GCC 3.2 *after* GCC 3.1 is released.

Please concentrate on GCC 3.1 to the best of your ability.  And please
think very carefully about the changes you make on the GCC 3.2 mainline.
It's really unfortunate that there have been, again, over a hundred
*regresssions from GCC 3.0* during GCC 3.1 development.

Please try to invest in infrastructure improvements that make it harder
to break the compiler.  Switching to GC is an example of this: it made
it harder to have memory errors.  Richard's verify_live_at_start stuff
is similar: it made it harder to have buggy optimizations.  The more
robust we can make our infrastructure the easier it will make it to move
forward with the new features and optimizations that everyone finds most
exciting.

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