As discussed on Issue #37628, we can flip a min/max node if we're subtracting from the sum of the node's operands
My main query is whether we need any oneuse limits or not - the only case where we don't see any reduction in instructions is if both the add + min/max have other uses, where we then replace a sub with a max/min intrinsic, which is probably going too far - any thoughts?
Use MinMaxIntrinsic + getInverseMinMaxIntrinsic() rather than enumerating cases?