GCC 3.3

[Mark Mitchell <mark at codesourcery dot com>]

As of 5PM PST tomorrow, all non-documentation changes to the 3.3 branch
will require my explicit approval.

I plan to make the first prerelease tarball shortly thereafter.

In my judgement, the current set of regressions against 3.3 contain no
show-stoppers.  There are certainly bugs that would ideally be fixed,
but I do not see anything that looks particularly worse than any other
release of GCC -- and there are a ton of fixes and improvements.

If you know of a regression for which you think we should hold the
release:

(1) Make sure that there is an open, high-priority PR for your problem
with 3.3 in the title.  If there is not such a PR, create one.  Do not
send me email before creating a PR; I cannot keep track of such emails.

(2) After making sure that a PR exists, tell me the number of the PR,
and why you think it is critically important to be fixed.  If there is a
patch available, please tell me that as well.  Holding up the release,
for a PR for which no patch is available, isn't very likely to happen;
you'll have to make a very strong argument.

(3) If I indicate that the PR is not worth holding the release, and you
believe otherwise, let me know; I will forward your request to the GCC
Steering Committee.

Thanks,

-- 
Mark Mitchell
CodeSourcery, LLC
mark at codesourcery dot com