> I can do this. What I also will do is improve VRP to still fold comparisons > of the for a - 10 > 20 when it knows there is no overflow due to available > range information for a (it doesn't do that right now).
I thought fold-const.c optimizes that right now and has been for a long time? If that's the case, I don't see why we should change it: we have absolutely no evidence of legacy code that would be affected and it's quite common due to macro substitution.
