https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61502
Harald van Dijk <harald at gigawatt dot nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |harald at gigawatt dot nl
--- Comment #2 from Harald van Dijk <harald at gigawatt dot nl> ---
DR#260 applies when using *p as if it is &y, just because it happens to compare
equal to it. For example, attempting to use it to read the value of y is not
permitted, even if guarded by an if (p == &y) condition. But that isn't the
case here: the pointer value &x + 1 is used in a way described in the standard
as the behaviour for the one-past-array values: the standard doesn't just
permit them to compare equal to an object immediately following it in memory;
what it does (because of the way it is worded) is require them to compare equal
to an object immediately following it in memory. (But I cannot even hazard a
guess as to whether that is intentional.)
