Gonzalo Paniagua Javier
Sat, 25 May 2002 02:27:14 +0200
* [ Serge <email@example.com>
* Fri, 24 May 2002 21:29:54 +0200 ]
> I think that the point is to use fast block move instructions if
> available (say, MOVS on x86), especially in the cases where
> size=const. Hence non-overlapping behaviour in the specs.
memcpy already takes care of copying in the fastest way posible. It has
a threshold (may be 8, can't remember now) and if the number of bytes to
copy is GE than the threshold, it uses movl. If not, it uses movb.