https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104356
--- Comment #38 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Andrew Macleod from comment #37) > As for ranger, range-ops will return UNDEFINED for the range if x is known > to be [0,0]. This can be propagated around, and depending on how it ends up > being used as to what happens with it. Yeah, so e.g. with Eric's patch to disable the X / boolean_range_Y simplifier in match.pd, won't the ranger perform the same optimization? I mean with the wi_fold_in_parts, if range of the divisor has 2 values and one of them is 0, won't it try to union range of X / 1 (range of X) and range of X / 0 (undefined) and yield range of X? So say won't 7 / Y_with_bool_range yield [7,7] ?
