https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62033
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Alan Modra from comment #2)
> I can see where you're coming from Andrew, but what is disconcerting about
> this is that the _FORTIFY_SOURCE warning is plainly incorrect here. How is
> one supposed to write a string.h memset macro using __builtin_constant_p()
> to provide a useful _FORTIFY_SOURCE warning, in the face of this sort of
> optimisation?
This is why Jakub moved it to the front-end away from glibc (See PR 61294).
>
> Users are going to see this as "__builtin_constant_p() is broken".
It is not. It is working correctly as on that path, it is constant.
This is an exact duplicate of bug 61294 really.
*** This bug has been marked as a duplicate of bug 61294 ***
