> Well, that's not equivalent. For instance, MPFR has many conditions > that evaluate to TRUE or FALSE on some/many implementations (mainly > because the type sizes depend on the implementation), even without > the assumption that an overflow cannot occur.
Can you give an example of such a condition and show how an optimization that assumed overflows were undefined could break that code?
