🚀 go-pugleaf

> > Hence implementation-defined behavior occurs.
> 
> Thus, the implementation has to say exactly how it handles this.
> There is still some question as to whether the implementation can
> define it as an overflow resulting in program termination, is there
> not?

Nope.  I requote:

*  From 3.10/1.6 (emphasis added):

#  Implementation-defined behavior -- behavior, for a CORRECT program
#  construct and CORRECT data, that depends on the characteristics of
#  the implementation and that each implementation shall document.

If the construct and data are correct, then it can't be correct to cause
program termination.
-- 
Mark Brader, msb@sq.com             "Logic is logic.  That's all I say."
SoftQuad Inc., Toronto                      -- Oliver Wendell Holmes

My text in this article is in the public domain.