https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
--- Comment #67 from post+gcc at ralfj dot de --- Does GCC document anywhere that it makes this assumption about memcpy? This is not part of the usual libc contract as far as I can tell. Neither POSIX nor the C standard allow calling memcpy with exact overlap, so it seems like GCC will not work with an arbitrary POSIX-compliant libc, it needs something more specific. Also, does the GNU libc document anywhere that it guarantees well-defined behavior for exact overlap?
