When an int is cast to a short and truncated, how is the new value determined?

by

According to the ISO C standard, when you convert an integer to a signed type, and the value is outside the range of the target type, the result is implementation-defined. (Or an implementation-defined signal can be raised, but I don’t know of any compilers that do this.)

In practice, the most common behavior is that the high-order bits are discarded. So assuming int is 32 bits and short is 16 bits, converting the value 0x1248642 will probably yield a bit pattern that looks like 0x8642. And assuming a two’s-complement representation for signed types (which is used on almost all systems), the high-order bit is the sign bit, so the numeric value of the result will be -31166.

int y   =   sx;

This also involves an implicit conversion, from short to int. Since the range of int is guaranteed to cover at least the entire range of short, the value is unchanged. (Since, in your example, the value of sx happens to be negative, this change of representation is likely to involve sign extension, propagating the 1 sign bit to all 16 high-order bits of the result.)

As I indicated, none of these details are required by the language standard. If you really want to truncate values to a narrower type, it’s probably best to use unsigned types (which have language-specified wraparound behavior) and perhaps explicit masking operations, like this:

unsigned int x = 0x1248642;
unsigned short sx = x & 0xFFFF;

If you have a 32-bit quantity that you want to shove into a 16-bit variable, the first thing you should do is decide how you want your code to behave if the value doesn’t fit. Once you’ve decided that, you can figure out how to write C code that does what you want. Sometimes truncation happens to be what you want, in which case your task is going to be easy, especially if you’re using unsigned types. Sometimes an out-of-range value is an error, in which case you need to check for it and decide how to handle the error. Sometimes you might want the value to saturate, rather than truncate, so you’ll need to write code to do that.

Knowing how conversions work in C is important, but if you start with that question you just might be approaching your problem from the wrong direction.

More Related Contents:

  1. what is meant by (void *) variable and (void *) & variable in C [closed]
  2. Can I change the datatype of previously declared variable in C?
  3. Do I cast the result of malloc?
  4. casting void** to 2D array of int – C
  5. “Pointer from integer/integer from pointer without a cast” issues
  6. Why cast an unused function parameter value to void?
  7. How to truncate a file in C?
  8. printf(“%p”) and casting to (void *)
  9. Should I explicitly cast malloc()’s return value? [duplicate]
  10. Is the behaviour of casting a negative double to unsigned int defined in the C standard? Different behaviour on ARM vs. x86
  11. printf specify integer format string for float
  12. When is casting between pointer types not undefined behavior in C?
  13. Casting one struct pointer to another – C
  14. Are C-structs with the same members types guaranteed to have the same layout in memory?
  15. casting char[][] to char** causes segfault?
  16. Mis-aligned pointers on x86
  17. Casting a pointer does not produce an lvalue. Why?
  18. Unexpected output of printf
  19. Dereferencing this pointer gives me -46, but I am not sure why
  20. Why / when to use `intptr_t` for type-casting in C?
  21. Casting one C structure into another
  22. What are the rules for casting pointers in C?
  23. How to print the name of the symbols of ELF files like the nm?
  24. What happens when I assign long int to int in C?
  25. How to cast an integer to void pointer?
  26. C Function to Convert float to byte array
  27. Is it Undefined Behaviour to cast away the constness of a function parameter?
  28. pow() cast to integer, unexpected result
  29. Is typecast required in malloc? [duplicate]
  30. Can I compare int with size_t directly in C?

Leave a Comment