The memmove page in release 2.79 states that a temporary copy is used in case the memory regions overlap. This is of course nonsense. The memory is either copied from front to back or from back to front. --- memmove.3.orig 2008-07-23 12:51:56.000000000 +0200 +++ memmove.3 2008-07-23 12:53:20.000000000 +0200 @@ -39,15 +39,7 @@ .BR memmove () function copies \fIn\fP bytes from memory area \fIsrc\fP to memory area \fIdest\fP. -The memory areas may overlap: copying takes place as though -the bytes in -.I src -are first copied into a temporary array that does not overlap -.I src -or -.IR dest , -and the bytes are then copied from the temporary array to -.IR dest . +The memory areas may overlap. .SH "RETURN VALUE" The .BR memmove () -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
