[Bug other/49194] Trivially stupid inlining decisions
egallager at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Mon Feb 11 00:55:00 GMT 2019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49194
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|hubicka at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #9)
> (In reply to Jan Hubicka from comment #8)
> > GCC 4.7 has now shrink wrapping that should reduce effect of inlining large
> > cold functions called once. Realistic testcases where we still kill code
> > quality would be welcome.
> >
> > I tested patch to disable inlining once for cold calls, but it does not help
> > in general. What happens is that we stop inlining
> > constructors/destructors/initialization loops that eventually kills code
> > quality of some benchmarks since known values are no longer propagated. I
> > will do more tunning of this for 4.8.
> >
> > Honza
>
> So are you still working on this then?
Guess not; unassigning
More information about the Gcc-bugs
mailing list