[Bug tree-optimization/17863] [4.0/4.1 Regression] threefold performance loss, not inlining as much

["mmitchel at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #27 from mmitchel at gcc dot gnu dot org  2005-10-31 00:37 -------
It seems unlikely to me that this is going to be release-critical, so I've
downgraded it to P4.

Our inlining heuristics are notoriously easy to perturb.  Probably, to do
substantially better, we'll need a more sophisticated cost model; or, as Jan
suggests, actually try inlining things see how much that helps.  I'm absolutely
certain that for every release we'll have at least one program that was inlined
worse than the previous release; the question is how we're doing overall, and
whether we're being particularly stupid.  So, I think the question is if we're
actually being particularly stupid on this test case.


-- 

mmitchel at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P4


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17863