5 ms·

The example the article gives isn't a general C problem, it's a common bug in some (mostly older) C/C++ compilers. As you point out GCC does not have this bug.

• haberman 14y ago
  It's not a bug, it's intended to be undefined behavior; see http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#614 http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html... (issue 1450)
  • mikeash 14y ago
    Regardless of undefined behavior, it should not crash the compiler.
    • haberman 14y ago
      Ah, I missed that it can crash the tcc compiler. Yeah, that's a bug.
      • mikeash 14y ago
        Probably easy to miss. One really does not expect the compiler to crash on code like that.