No, that's clang/llvm; gcc handles this correctly (at least by the extremely low standards of gcc/llvm handling of undefined behaviour): $ gcc test.c test.

No, that's clang/llvm; gcc handles this correctly (at least by the extremely low standards of gcc/llvm handling of undefined behaviour): $ gcc test.c test.c:3:5: error: jump into statement expression