https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67999
Florian Weimer <fw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=63303
--- Comment #26 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #12)
> (In reply to Daniel Micay from comment #10)
> > (In reply to Florian Weimer from comment #7)
> > > If this is not a GCC bug and it is the responsibility of allocators not to
> > > produce huge objects, do we also have to make sure that no object crosses
> > > the boundary between 0x7fff_ffff and 0x8000_0000? If pointers are treated
> > > as de-facto signed, this is where signed overflow would occur.
> >
> > No, that's fine.
>
> Is this based on your reading of the standard, the GCC sources, or both?
> (It is unusual to see people making such definite statements about
> middle-end/back-end behavior, that's why I have to ask.)
As I suspect, the claim that this is fine seems to be incorrect, see bug 63303
comment 13.
