Richard Guenther writes: > > The problem in this PR is that code like in the testcase (from > OpenOffice) assumes that pointer overflow is defined. As the > standard does not talk about wrapping pointer semantics at all (at > least I couldn't find anything about that), how should we treat > this?
Look at Section 6.5.6, Para 8. The code is undefined. Andrew.