On 8/12/20 12:12 PM, Bruno Haible wrote:
why would this matter? This is C code, not C++ code.

My guess is that it matters with picky implementations intended for debugging. The C standard allows implementations to trap when an out-of-range value is converted to a signed integer, and some debugging implementations do that. See, clang's new -fsanitize=implicit-signed-integer-change option for an example.

Reply via email to