This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/32667] block copy with exact overlap is expanded as memcpy
- From: "lopresti at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 25 Apr 2016 16:12:21 +0000
- Subject: [Bug middle-end/32667] block copy with exact overlap is expanded as memcpy
- Auto-submitted: auto-generated
- References: <bug-32667-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32667
--- Comment #16 from Patrick J. LoPresti <lopresti at gmail dot com> ---
Well, Valgrind itself is another real-world example. Tools like Valgrind cannot
distinguish invalid memcpy() calls by the programmer from invalid memcpy()
calls emitted by GCC.
You can, of course, redefine every standard interface you like and simply
document it. That would be awful engineering -- as in this case -- but you
could do it.