What is the defined behavior in C for UINT_MAX + 1u
? How safe is to assume it is zero?
UINT_MAX is the maximum value for an object of type unsigned int.
A signed integer is a 32-bit datum that encodes an integer in the range [-2147483648 to 2147483647].
From the standard (C11, 6.2.5/9, emphasis mine):
[...] A computation involving unsigned operands can never overflow, because a result that cannot be represented by the resulting unsigned integer type is reduced modulo the number that is one greater than the largest value that can be represented by the resulting type.
If UINT_MAX
is 10
:
(10 + 1) % (10 + 1) == 0
So, yes, it's safe to assume it's zero.
It's worth emphasizing that while unsigned behavior is well-defined, signed integer overflow isn't:
In the C programming language, signed integer overflow causes undefined behavior, while unsigned integer overflow causes the number to be reduced modulo a power of two
A very good paper on the subject:
EXAMPLES OF C/C++ INTEGER OPERATIONS AND THEIR RESULTS
Expression Result
---------- ------
UINT_MAX+1 0
LONG_MAX+1 undefined
INT_MAX+1 undefined
SHRT_MAX+1 SHRT_MAX+1 if INT_MAX>SHRT_MAX, otherwise undefined
char c = CHAR_MAX; c++ varies
-INT_MIN undefined
(char)INT_MAX commonly -1
1<<-1 undefined
1<<0 1
1<<31 commonly INT_MIN in ANSI C and C++98; undefined in C99 and C++11
1<<32 undefined
1/0 undefined
INT_MIN%-1 undefined in C11, otherwise undefined in practice
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With