https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115097
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> Why do we use
> tail-calls here instead of aliases?
The functions are exported, so we can't prove if some other TU won't do
return &test1 == &test2;
or similar.
> Why do we inline back?
But IMHO if we ICF optimize something, we shouldn't undo that, so should
disable the inlining across that edge. Or decide not to ICF optimize it.
Plus we have the similar problem with fnsplit, where if we split some function
and inline it back it causes undesirable debug info differences, ideally the
inlining of fnsplit into self should just restore the old body.
