Fri, 24 May 2002 23:21:26 +0300
> presumably memmove(3) does this, right?
But what I mean is:
a) inlining the code when size=const, in some cases avoiding use of counter reg.
Say, if size=8 that would be two movsd instructions (no need to load ECX);
(Same for small sizes - no need to use EDI/ESI).
b) avoiding compare & conditional branch that is always present in memmove (and is slow);
Anyhow, introducing incompatibility seems unjustified in this case.
(I mean some code will work on Mono, but not on .NET).