GCC 4.2.0 Status Report (2007-03-04)

Mark Mitchell mark@codesourcery.com
Mon Mar 5 04:45:00 GMT 2007

After reviewing all of the traffic[1] that stemmed from my previous
status report, I've decided that, indeed, it makes sense to steam ahead
with GCC 4.2.0 based on current GCC 4.2.0 release branch.

I haven't yet made a final decision on the aliasing issue, and I'm open
to suggestions about what to do there, but I do think it makes sense to
proceed with the release.  I still hope to build RC1 a week from today.

However, I do think that it's important to eliminate some of the 139
open P2 and P1 regressions [2], especially those P1 regressions which
did not appear in GCC 4.1.x.

I think it's reasonable to ask that those in the MAINTAINERS file as
having write privileges contribute at least one fix to the 4.2 branch,
in the next week, unless there are no regressions in your area of the
compiler.  A la Stephen Colbert, I'll be tipping my hat or wagging my
finger in my report next Monday. :-)  Of course, that's not to say that
non-maintainers shouldn't contribute as well!

Let's get it done!

Mark Mitchell
(650) 331-3385 x713

[1] http://gcc.gnu.org/ml/gcc/2007-02/msg00427.html


More information about the Gcc-patches mailing list