[Bug middle-end/83665] [8 regression] Big code size regression and some code quality improvement at Jan 2 2018
hubicka at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Mon Jan 8 16:51:00 GMT 2018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83665
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org
--- Comment #9 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I have noticed that accidental change and plan to deal with it while retuning
inliner now.
I think overall the problem is caused by the fact that old code capped time to
10000. This means that most larger functions was estimated to have time 10000
and inlining seemed to produce no speedup.
With sreals we keep the ratios more realistic and see more benefits from
inlining and thus get big speedup more often. I will see what I can do with
the default value wrt code size.
Thanks for bisecting this!
More information about the Gcc-bugs
mailing list