Andrew Pinski wrote:
But there are still issues.
PR 23691 is one of them which beaks boost.
I wasn't aware that there were still issues. Please assign me to PRs
that represent things I've broken; I'll fix them, or at least explicitly
unassign myself if I feel unfairly blamed.
In any case
On Sep 7, 2005, at 11:21 AM, Mark Mitchell wrote:
Paolo Bonzini wrote:
There's no special freeze for the 4.0 branch at this point; we'll
leave it in regression-fixes only mode. The branch will freeze when
I create the first release candidate.
Some of your C++ fixes have been quite invasive.
Paolo Bonzini wrote:
There's no special freeze for the 4.0 branch at this point; we'll
leave it in regression-fixes only mode. The branch will freeze when I
create the first release candidate.
Some of your C++ fixes have been quite invasive. Maybe it's too much
haste to spin the rc befor
There's no special freeze for the 4.0 branch at this point; we'll leave
it in regression-fixes only mode. The branch will freeze when I create
the first release candidate.
Some of your C++ fixes have been quite invasive. Maybe it's too much
haste to spin the rc before the bugs can be detec
Simply put, it's time for another GCC 4.0.x release.
There are 48 critical bugs open against 4.0.1 and some nearly 200
regressions. I've not done a complete triage, so I can't say how many
of these might be incorrectly targeted. Fewer than 20 are wrong-code,
which is still more than I'd like
