On Mon, 15 Mar 2010, Jeff Law wrote: > On 03/15/10 10:18, Richard Guenther wrote: > > Status > > ====== > > > > The trunk is still in stage 4 which means it is open under the usual > > release branch rules. Thus the trunk is open for regression and > > documentation fixes only. > > > > There are currently 16 P1 bugs that block the release. If you are > > assigned to any P1 GCC 4.5 regression please either work on them > > or unassign yourself. We have been in stage 4 for three and a half > > month now, so you can expect that some bugs that are now P1 will > > be downgraded to P2 at the point a release candidate is made > > available, simply to not block the release of 4.5.0 forever. > > As maintainers do not care for P1 bugs in their maintainance area > > so will the release managers not consider them P1. > > > > The following is a list of P1 GCC 4.5 regressions that look serious > > enough to myself to ping them explicitly here: > > > > 42509, arm-gnueabi doesn't bootstrap but is a primary target > > 43873, var-tracking deadlocks > > 43087, C++ ICE in tsubst > > 43206, C++ ICE in cp/pt.c:9249 > > 43300, ICE during SSA expand > > 43333, C++ __is_pod is broken > > 43365, EH lowering/optimization causes wrong-code > > 43375, ICE caused by the new vector type mangling > > > > Overall GCC 4.5 does not look bad. But we are still sorting out > > VTA related bugs (and improvements as it appears to me). > > > FWIW, it might be helpful to include the list of _all_ P1s in these reports -- > there may be people that have some time to help out, but don't know precisely > which bugs are the most critical right now.
The rest of the P1 are 41371, var-tracking slowness (fixed, waiting for more testcases) 42181, wrong-code with -fgraphite-identity 42450, cgraph checking ICE, patch available 42917, -fcompare-debug failure with -ftree-loop-linear, patch available 42977, -fcompare-debug failure with even more weird flags 43051, debug quality issue with VTA 43058, var-tracking using up all virtual memory on 32bit hosts 43092, debug correctness issue with VTA Bugzilla queries for all P1 GCC 4.5 regressions is http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=4.5&target_milestone=4.3.0&target_milestone=4.3.1&target_milestone=4.3.2&target_milestone=4.3.3&target_milestone=4.3.4&target_milestone=4.3.5&target_milestone=4.3.6&target_milestone=4.4.0&target_milestone=4.4.1&target_milestone=4.4.2&target_milestone=4.4.3&target_milestone=4.4.4&target_milestone=4.4.5&target_milestone=4.5.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&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfiel dvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&query_based_on=4.5+blocker&field0-0-0=noop&type0-0-0=noop&value0-0-0= Richard.
