So really, the "something sane" that you are talking about should be issuing an error or warning.
The reasoning for having it an extension is mainly so that current code can be trivially ported.
If you don't... maybe. But do you realistically think "paranoid C" would ever get its library ecosystem up to a level where it matched e.g. OCaml? Do you think embedded vendors would be more likely to support it (the other big use case for C)? If you're going to be switching libraries anyway, OCaml is a much nicer language to work in.
(On a side note. I like OCaml, but don't like the syntax. I wish there was a language out there that was basically OCaml with c-like syntax. Or rather, I wish language syntax in general was less coupled with language semantics. It should be possible, and is, to, for example, automatically convert between Pythonic-style indentation and C-style braces and lisp-esque braces. Define the language in terms of an AST and leave the syntax up to the editor.)
[1] http://stackoverflow.com/questions/12887700/can-code-that-is...
All it's doing is saying that "my compiler uses the freedom to do anything that undefined behavior grants to do something sane".
By definition, anything that would be broken by such a change was already undefined behavior.