GCC 4.0 Status Report (2005-04-05)

Mark Mitchell mark@codesourcery.com
Mon Apr 4 23:26:00 GMT 2005


I've attached a revised summary of the critical bugs open against 4.0. 
The good news is that there are fewer than last week.  There are several 
  bugs for which it appears that all that remains to be done is apply a 
mainline patch to the 4.0 branch.  These are listed at the bottom of the 
summary.

There are three outstanding bugs (19317, 19312, 18604) assigned to Jason 
Merrill, but I didn't hear back from him last week.  Jason, I'm going to 
assume that you're unable to work on these.  As Nathan is on vacation, I 
suppose that means that these will fall to me to fix.  If anyone else 
would like to volunteer for 19317, which has proven particularly thorny, 
that would be helpful.

It would also be helpful if someone were able to review Alexandre 
Oliva's patches for 20126 and 20739.

In terms of schedule, I plan to create the first prerelease this 
weekend, in preparation for a final release on or about the 15th, as 
planned.  After I make the prerelase, the branch will be slushy, and all 
non-documentation commits will require my approval.

I will also clarify an issue about testcases that Joseph raised 
privately.  In particular, fixes to testcases (like adding a new target 
on which to skip the test) are OK for 4.0 if they are OK for mainline, 
without my approval.  In general, things that do not affect the compiler 
or the build process do not require my approval.  Indeed, fixing 
testcases so that there are fewer unexpected failures is helpful both to 
me and to users who will build the release.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: gcc-20050405.txt
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20050404/697f9fbd/attachment.txt>


More information about the Gcc mailing list