And yet, in practice the C have written over the last 20+ years mostly ended up with "undefined behaviour" = "what CPU does"... That may not be true in fact bu

And yet, in practice the C have written over the last 20+ years mostly ended up with "undefined behaviour" = "what CPU does"... That may not be true in fact but it ends up that way because "undefined behaviour" tends to be implemented "to work" and we're used to behaviour of common CPUs that may have fed into expectation of what "to work" should be...