1Hardgeneralโฑ 45sWhat is undefined behavior caused by signed integer overflow in C?๐โผAIt always wraps around like unsigned integersBThe C standard leaves the result unspecified, and compilers may optimize assuming it never happensCIt always raises a runtime exceptionDIt is defined to saturate at INT_MAX
2Hardgeneralโฑ 45sWhy can a strict-aliasing violation cause miscompilation in optimized C code?๐โผAThe compiler always inserts a runtime checkBThe compiler assumes pointers of different incompatible types never alias the same memory, enabling reordering/optimizations that break code violating that assumptionCAliasing is only a linker-time concernDGCC and Clang ignore the aliasing rule by default