Signed integer overflow check optimized away in C
Signed integer overflow guard disappears after optimization ISO C defines signed integer overflow as undefined behavior. A compiler may assume the overflow never occurs and remove an explicit overflow check, even when the source appears to guard against it. I need to know whether a bounds check written for signed arithmetic can be relied upon across common C