Unexpected Output When Using Bitwise Operations on Unsigned Integers in C
I'm performance testing and I'm a bit lost with I'm working with unexpected behavior when performing bitwise operations on unsigned integers in C... Specifically, I'm trying to set certain bits in an unsigned integer but the output isn't what I anticipated. Here's a simplified version of my code: ```c #include <stdio.h> int main() { unsigned int num = 0x0F; // 0000 1111 in binary unsigned int mask = 0xF0; // 1111 0000 in binary unsigned int result; result = num | mask; printf("Result: 0x%X\n", result); return 0; } ``` In this code, I expect the final result to be `0xFF` (which is 1111 1111 in binary) after applying the bitwise OR operation. However, the output I'm getting is `0xF0`, which is confusing to me. I've double-checked the values of `num` and `mask`, and they seem correct. I also tried using the bitwise AND and XOR operations, but they seem to yield similar unexpected results. I suspect this might be related to how I am interpreting the output, but I need to quite figure it out. Could there be something I'm missing about how bitwise operations work with unsigned integers, or is there a potential scenario with my compiler settings? I'm using GCC 10.2 on a Linux environment. Any insights would be greatly appreciated! I'm working on a service that needs to handle this. Any help would be greatly appreciated! For context: I'm using C on Windows 11. Any ideas how to fix this? This is my first time working with C 3.10. I appreciate any insights!