--- Additional Comments From giovannibajo at libero dot it 2005-03-02
21:28 ---
OK let's close this as fixed then. Many thanks to the hard work of the whole
GCC team!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17278
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-03-02
21:27 ---
Fixed.
--
What|Removed |Added
Status|NEW |RESOLVED
--- Additional Comments From kgardas at objectsecurity dot com 2005-03-02
21:25 ---
Subject: Re: [4.0/4.1 Regression] 8% C++ compile-time
regression in comparison with 3.4.1 at -O1 optimization level
I agree with Giovanni that both #17278 and #13776 are fixed from MICO
compile-time re
--- Additional Comments From giovannibajo at libero dot it 2005-03-02
21:21 ---
At this point, I think we could safely close this and related bugs. Karel
could continue to periodically test GCC and report new regressions in new
bugs. I don't think keeping these open bring us any benefi
--- Additional Comments From kgardas at objectsecurity dot com 2005-03-02
20:05 ---
Subject: Re: [4.0/4.1 Regression] 8% C++ compile-time
regression in comparison with 3.4.1 at -O1 optimization level
New results for 4.0.0 20050301 are posted here:
http://gcc.gnu.org/ml/gcc/2005-03/ms
--- Additional Comments From kazu at cs dot umass dot edu 2005-03-01 15:08
---
Karel, could you retest the testcase with the gcc-4.0 branch?
Several speed-up patches went in after your last benchmark.
Thanks,
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17278