Re:Memcpy vs. memmove
by makomk on Monday December 01, 2014 @07:28PM
(#8685019)
The issue that caused Linus to argue memcpy should just act like memmove involved old binaries breaking with new kernels, so the compiler's behaviour wasn't an issue there.
[ Parent
| on HN ]
It was a bit more than that. He implied that the performance differences were trivial, so it wasn't worth the trouble.
I think, unfortunately, Linus' argument amounts to demanding that API's conform to how they are used rather than how they are specified, which leads to O_PONIES type problems.
It was a change in libc, not the kernel. Someone ran valgrind and found the binary-only flash plugin was depending on the undefined memcpy behaviour.
Linus was butting in because a kernel sound driver regression was also suspected earlier...