I think you are in agreement with the comment you are replying to.
Re:Signed Integers Are Two’s Complement
by paulddraper on Wednesday May 30, 2018 @11:18PM
(#17193711)
The comment suggested the standard make it implementation defined rather than undefined. There's not a meaningful difference here.
Even today, an implementation may define unsigned overflow.
Yes, there is. Implementation defined means that a conforming implementation _must_ document its behavior.
That means that programmers don’t have to use trial and error to figure out how the compiler behaves and don’t have to _hope_ they found all the corner cases.
And that is how we get #if defined(_THIS_THING_SOME_COMPILER_DEFINES) && !defined(__BUT_NOT_THIS_ONE_THAT_COMPILER_X_DEFINES) soup ;)
Re:Signed Integers Are Two’s Complement
by greenhouse_gas on Thursday May 31, 2018 @12:19PM
(#17197534)
Better than than silently ignoring an if guard preventing an overflow, and then overflowing anyways on addition.
Oh, I see, I wonder if greenhouse_gas is suggesting a feature similar to sizeof() that can be used to portably adapt your program's design to the target's overflow capability.
Nothing is stopping your C compiler from making the guarantee sizeof(int)=4 on x86/amd64.