On Fri, Apr 08, 2016 at 09:14:33PM +0200, Richard Biener wrote:
> Hmm, I think this means GIMPLE_has_side_effects is to be fixed then.
> Note that honza had plans to compute things like 'uses FP' and 'contains
> arith with undefined overflow' and propagate that alongside pure/const-ness.
>
> Can you try to asses the impact of fixing no-side-effects?
That sounds extremely risky to me, there are lots of callers of that, and
many really don't care, they e.g. check if they can remove the stmt, or
if it can be moved towards the exit block, etc.
Plus even other side-effects like maybe throwing are not included in
gimple_has_side_effects and are tested separately.
Maybe just return true on all calls in gimple_could_trap_p, but even that
has 5 other callers that would need to be carefully analyzed. Even that
looks too risky for late stage4 to me.
Jakub
