News for hackers. Stuff that matters.
Re:Signed Integers Are Two’s Complement by yoklov on Thursday May 31, 2018 @09:26AM (#17196090)
This isn’t entirely untrue in theory, but in practice it is. Compilers optimize under the assumption that undefined behavior never occurs, and the standard is written with this assumption. Any conforming compiler is free to break code that relies on this.

Typically, behavior that reasonably may vary from compiler/machine is considered implementation defined, and not undefined.

Re:Signed Integers Are Two’s Complement by kazinator on Thursday May 31, 2018 @09:51AM (#17196272)
> Any conforming compiler is free to break code that relies on this.

Ah, but, for example, __attribute__((packed)) is undefined behavior; is the compiler free to break that?

This "free to break" is a juvenile fiction based on the idea that the only document that applies is ISO C; there is no other contract or promise between user and implementor.

Re:Signed Integers Are Two’s Complement by sanxiyn on Thursday May 31, 2018 @10:03AM (#17196360)
GCC documentation is another such contract, which provides -fwrapv. If you want -fwrapv, use -fwrapv.