x86, mem: Don't implement forward memmove() as memcpy()
authorMa, Ling <ling.ma@intel.com>
Mon, 23 Aug 2010 21:11:12 +0000 (14:11 -0700)
committerH. Peter Anvin <hpa@linux.intel.com>
Mon, 23 Aug 2010 21:14:27 +0000 (14:14 -0700)
memmove() allow source and destination address to be overlap, but
there is no such limitation for memcpy().  Therefore, explicitly
implement memmove() in both the forwards and backward directions, to
give us the ability to optimize memcpy().

Signed-off-by: Ma Ling <ling.ma@intel.com>
LKML-Reference: <C10D3FB0CD45994C8A51FEC1227CE22F0E483AD86A@shsmsx502.ccr.corp.intel.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>

No differences found