Re: [PATCH] c++/67376 Comparison with pointer to past-the-end, of array fails inside constant expression

[Jeff Law <law@redhat.com>]

On 03/21/2016 11:54 AM, Jason Merrill wrote:
>>> Both b0 and b1 are invalid and should be diagnosed, but only b1
>>> is.  b1 isn't because because by the time we see its initializer
>>> in constexpr.c it's been transformed into the equivalent of "b1
>>> = (int*)ps" (though we don't see the cast which would also make
>>> it invalid).
>>>
>>> But if we can avoid these early simplifying transformations and
>>> retain a more faithful representation of the original source then
>>> doing the checking later will likely be simpler and result in
>>> detecting more problems with greater consistency and less effort.
>> Do we know where the folding is happening for this case and is it
>> something we can reasonably defer?    ie, is this just a case we missed
>> as part of the deferred folding work and hence should have its own
>> distinct BZ to track?
>
> Yes, why is it already folded?
Let's pull that out into a separate BZ and tackle it for gcc-7.

jeff