If we can detect that saturating math that depends on an IV cannot overflow, replace it with simple math. This is similar to the CVP optimization from D62703, just based on a different underlying analysis (SCEV vs LVI) that catches different cases.
One case this doesn't handle yet is if the IV calculation itself uses a saturating counter.
Hm, this is because we didn't deal with non-ExtractValueInst uses of WO?
Since we know the overflow won't happen, those can be simply folded to a single insert, no?