https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65701
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-04-09
Ever confirmed|0 |1
--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
The difference in inlining decision is
(- is with patch reverted, + is current mainline):
Why inlining failed?
-function body not available : 568 calls, 4150392
freq, 0 count
---param large-function-growth limit reached : 3 calls, 3000
freq, 0 count
+function body not available : 568 calls, 3750333
freq, 0 count
+--param large-function-growth limit reached : 2 calls, 101000
freq, 0 count
--param large-stack-frame-growth limit reached : 1 calls, 1000
freq, 0 count
---param max-inline-insns-auto limit reached : 37 calls, 265369
freq, 0 count
+--param max-inline-insns-auto limit reached : 37 calls, 275141
freq, 0 count
that actually means a lot of changes in the particular inlining decisions,
because several large functions gets inlined differently.
The beggining of inline changes seems as expected - the growths are corrected
on mainline and thus we start considering functions in different order.
I will need to profile this
