On Tue, 16 Jul 2019 11:28:29 -0700 Nick Desaulniers <[email protected]> wrote:
> The cited code looks like a check comparing that the pointer distance > is greater than the size of bytes being passed in. I'd wager > someone's calling memmove with overlapping memory regions when they > really wanted memcpy. Maybe a better question, is why was memmove > ever used; if there was some invariant that the memory regions > overlapped, why is that invariant no longer holding. I'm confused by the above statement as memmove() allows overlapping of src and dest, where as memcpy() does not. -- Steve
