https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ebotcazou at gcc dot gnu.org
--- Comment #70 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> And worse, glibc uses "restrict" in its "memcpy", which according to GCC's
> semantics means glibc *cannot* make such a guarantee without removing
> "restrict". Arguably there is still a bug in GCC here: the assumption GCC
> makes about memcpy is in contradiction with GCC's own specification (as
> inherited from the C standard) for what the standard signature of memcpy
> means when compiled with GCC.
No, there is no bug in GCC, since it effectively does not apply "restrict" to
the internal calls to memcpy it generates.
