https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70586
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Yep, pure/const function can trap and even throw an exception. We could cleanup
the way we store information about function body and propagate info whether
function can do trap/eh exception and such.
I wonder how desirable is however to turn code path that doesn't call function
into a code path that does. Is it a win?
Shouldn't tree-ssa-ifcombine have some cost model that should have caught this
and decide it unprofitable? Const/pure functions can be very slow.
Honza
