Comparison operation on unsigned and signed integers

by

Binary operations between different integral types are performed within a “common” type defined by so called usual arithmetic conversions (see the language specification, 6.3.1.8). In your case the “common” type is unsigned int. This means that int operand (your b) will get converted to unsigned int before the comparison, as well as for the purpose of performing subtraction.

When -1 is converted to unsigned int the result is the maximal possible unsigned int value (same as UINT_MAX). Needless to say, it is going to be greater than your unsigned 1000 value, meaning that a > b is indeed false and a is indeed small compared to (unsigned) b. The if in your code should resolve to else branch, which is what you observed in your experiment.

The same conversion rules apply to subtraction. Your a-b is really interpreted as a - (unsigned) b and the result has type unsigned int. Such value cannot be printed with %d format specifier, since %d only works with signed values. Your attempt to print it with %d results in undefined behavior, so the value that you see printed (even though it has a logical deterministic explanation in practice) is completely meaningless from the point of view of C language.

Edit: Actually, I could be wrong about the undefined behavior part. According to C language specification, the common part of the range of the corresponding signed and unsigned integer type shall have identical representation (implying, according to the footnote 31, “interchangeability as arguments to functions”). So, the result of a - b expression is unsigned 1001 as described above, and unless I’m missing something, it is legal to print this specific unsigned value with %d specifier, since it falls within the positive range of int. Printing (unsigned) INT_MAX + 1 with %d would be undefined, but 1001u is fine.

More Related Contents:

  1. Why is a negative int greater than unsigned int? [duplicate]
  2. Unsigned hexadecimal constant in C?
  3. Running C — helloWorld runs but nothing else — Ubuntu
  4. Why does malloc initialize the values to 0 in gcc?
  5. Why does integer division by -1 (negative one) result in FPE?
  6. Can’t compile a C program on a Mac after upgrading to Catalina 10.15
  7. How can I tell gcc not to inline a function?
  8. Is it possible to tell the branch predictor how likely it is to follow the branch?
  9. What does it mean to align the stack?
  10. Looping over arrays with inline assembly
  11. warning: incompatible implicit declaration of built-in function ‘xyz’
  12. printf not printing on console
  13. Why am I getting a gcc “undefined reference” error trying to create shared objects?
  14. gcc: printf and long double leads to wrong output. [C – Type conversion messes up]
  15. Drawing a character in VGA memory with GNU C inline assembly
  16. How do I fix “for loop initial declaration used outside C99 mode” GCC error?
  17. Why does the compiler allocate more than needed in the stack?
  18. What are the useful GCC flags for C?
  19. Which compiler should I trust?
  20. Why am I able to perform floating point operations inside a Linux kernel module?
  21. Anonymous functions using GCC statement expressions
  22. What is -ffreestanding option in gcc?
  23. why does GCC __builtin_prefetch not improve performance?
  24. Linking a C program directly with ld fails with undefined reference to `__libc_csu_fini`
  25. execute binary machine code from C
  26. Compare 16 byte strings with SSE
  27. Returning struct containing array
  28. Compiling a C program that uses OpenGl in Mac OS X
  29. Why does malloc allocate a different number of bytes than requested?
  30. & operator optional in function pointer assignment

Leave a Comment