This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
GCC 4.3.0 Status Report (2007-06-29)
- From: Mark Mitchell <mark at codesourcery dot com>
- To: GCC <gcc at gcc dot gnu dot org>
- Cc: Daniel Berlin <dberlin at dberlin dot org>
- Date: Fri, 29 Jun 2007 13:49:48 -0700
- Subject: GCC 4.3.0 Status Report (2007-06-29)
We have spent the last two weeks in lockdown, hopefully fixing
regressions.
At this point, there are 153 P3 and higher regressions open against GCC
4.3.0. In reviewing those, I was struck by how many are in fact new
regressions in 4.3 -- problems that did not occur in previous releases.
These include a number of P1 problems such as:
* Failure to bootstrap on relatively common platforms (e.g., PR32540)
* Failure to correctly compile SPEC benchmarks (e.g., PR32303)
* ICEs on various applications
See the full list here:
http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=4.3&target_milestone=4.0.4&target_milestone=4.1.3&target_milestone=4.3.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=
It's clear that the dataflow and PTR_PLUS changes, while of course
beneficial, have (as we all expected) caused a bit of collateral
fallout. I think it's very important that we step up to fix these
problems now, while fresh in our minds.
That said, I think it's time to enter Stage 2. So, effective
immediately, the lockdown is over. As stated previously, I intend to
reenter the lockdown mode every so often, in order to help us focus on
closing regressions.
Danny, I would still appreciate your help in setting up additional
fields in Bugzilla that we can use to help make people aware of
regresions that they have caused
Previous Report: http://gcc.gnu.org/ml/gcc/2007-06/msg00411.html
Thanks,
--
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713