Race conditions are undefined behavior though. It's even included in that post you just linked as an example of undefined behavior.

> There are many other kinds of course, including sequence point violations like "foo(i, ++i)", race conditions in multithreaded programs, violating 'restrict', divide by zero, etc.

(And no, volatile does not save you.)