The GCC 4.1 branch is now closed and should have no further commits. All open bugs at the 4.1.3 milestone, or marked as [4.1/4.2/4.3/4.4 Regression] or similar, have been updated accordingly.
In going though these bugs, I noticed that many were marked as ASSIGNED, or as having patches, but had seen no recent activity. If a bug is assigned to you but you do not plan to do any further work on it (including if you fixed it on trunk but do not plan to backport the fix), please unassign yourself from the bug. If you have a patch for a bug that has not been reviewed, you need to make sure it has been posted to gcc-patches, then keep pinging it on gcc-patches every week or two until it is reviewed. Some bugs could be closed as fixed long ago even though the regression markers on them didn't indicate this; it may be useful for maintainers of parts of the compiler to go through relevant open bugs, confirming UNCONFIRMED ones and closing bugs that have been fixed on trunk (in the case of non-regressions) or on all open branches (in the case of regressions) and updating regression status for regressions fixed in some places but not everywhere. The 4.2 branch remains open with no plans for further releases. It should probably be closed around the time the 4.4 branch is created in the absence of a volunteer to maintain it and build releases beyond then. Previous 4.1 status report: http://gcc.gnu.org/ml/gcc/2007-05/msg00669.html -- Joseph S. Myers [EMAIL PROTECTED]
