This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug tree-optimization/17863] [4.0/4.1 Regression] threefold performance loss, not inlining as much
- From: "hubicka at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 31 Oct 2005 18:36:03 -0000
- Subject: [Bug tree-optimization/17863] [4.0/4.1 Regression] threefold performance loss, not inlining as much
- References: <bug-17863-2109@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #28 from hubicka at gcc dot gnu dot org 2005-10-31 18:36 -------
I get 0m8.052s on 3.4 and 0m8.127s on mainline on Athlon. This hardly counts
as an regression.
This is actually effect of some cost tweaks we did relatie to gimplifier a
while ago.
Reduced testcase fits in limits now too.
Unlike Mark I would not claim that our inliner heuristics are actually more
notorious than any others ;))
--
hubicka at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17863