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 CodeSourcery [EMAIL PROTECTED] (650) 331-3385 x713 [1] http://gcc.gnu.org/ml/gcc/2007-02/msg00427.html [2] http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=4.2&target_milestone=4.0.4&target_milestone=4.1.3&target_milestone=4.2.0&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&gcchost_type=allwordssubstr&gcchost=&gcctarget_type=allwordssubstr&gcctarget=&gccbuild_type=allwordssubstr&gccbuild=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=
