On 11/15/22 09:31, Aldy Hernandez via Gcc-patches wrote:
I know it's past the end of stage1, but I'm afraid we'll drag this
around forever in the GCC12 branch, and it's an easy readbility fix.
p.s. Or if you prefer:
if (!lb_nan && !ub_nan && !maybe_nan && ....)
r.clear_nan ();
OK for trunk?
gcc/ChangeLog:
* range-op-float.cc (range_operator_float::fold_range): Make check
for maybe_isnan more readable.
Your call. I think we're so early in stage3 that if you think this is uber-safe go for it.
jeff
