On 07/26/2015 07:05 PM, Kugan wrote:
I thought that when !gimple_assign_cast_p (stmt), RHS will always
boolean. I have now added this check in the attached patch.
Thanks.
I also noticed that in maybe_optimize_range_tests, GIMPLE_COND can
have non compatible types when new_op is updated
(boolean types coming from tcc_compare results) and hence need to be
converted. Changed that as well.
Did you find this by examination or with some testcode? If the latter,
including a testcase for this issue would be appreciated.
Bootstrapped and regression tested on x86-64-none-linux-gnu with no new
regressions. Is this OK for trunk?
OK with an updated changelog.
Jeff
