You could make a case that it's a bug in the standard though :-)
A standard is needed in some cases where there is no 'obvious' behavior.
I think this is the way that the 'Ruby standard' is defined, by a reference implementation which is assumed to be bug-free.
About the interpretation of the standard: this is probably true, but this kind of technical documents is meant to be mono-interpretable, if you know what I mean. Ultimately there might be a few limitations which you don't encounter in practice (if you give your variables names of more than 4k characters, I doubt if it will compile), so you might argue this is an 'interpretation of the standard'.
I would argue that in such a case technically, the compiler doesn't comply with the standard, but for all purposes and intents, it does (and so, in practice no one would doubt that the compiler complies to the standard).
Erm ... nope. If code is unreachable, it can, by definition, not exhibit undefined behaviour.
> The reason it doesn't simply abort is because compiler authors don't go out of their way to do extra work for no reason.
Well, true, but the primary reason is that there are parts of the input domain for which the behaviour of the code is actually defined, and it's not defined to mean a call to abort(). The mere possibility to call some code at runtime with values for which the behaviour is undefined does not make the code's semantics completely undefined.