
16 Apr
2012
16 Apr
'12
5:16 p.m.
Michael Kochetkov wrote:
I'm using VC++2005 though.
I do remember that at least memcpy intrinsic worked pretty smart in that compiler.
It does. I think I see what's going on. memcmp has to return -1, 0 or 1. This is why it does an initial DWORD loop to find the first mismatch, then does a byte compare to determine the return value.