3 ms·
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
by makomk 12y ago
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.
- cbsmith 12y agoIt 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.
- fulafel 12y agoIt 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...