------- Comment #19 from falk at debian dot org 2009-03-18 09:06 ------- (In reply to comment #18) > I can't imagine an implementation of memcpy that would break when the two > addresses are the same, it just doesn't work if one is offset but > overlapping. > So the valgrind warning is pedantically correct, but I think it doesn't > indicate a real safety issue.
As I mentioned in comment #6, it could go wrong if memcpy uses "cache prefetch with write intent" instructions. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39480
