On 6/2/26 9:00 AM, Richard Biener wrote:
niter analysis is now set up to work with passes having ranger enabled and ranger allows analysis of GENERIC expressions via range_of_expr just fine (it needs a context stmt though). I suggest to rework to make use of that instead of walking stmts in niter as that seems wrong to me.
Thank you for the suggestion. I’ve reworked the patch to remove the SSA_NAME restriction in determine_value_range and to pass the loop-header statement as the ranger context. This gives the more precise bounds I was looking for while keeping the change much simpler.
Please could you take a look at the updated version?
Another possibility would be to make expand_simple_operations also track/combine value-range of the result, but I think this shouldn't be needed. Richard.
