28 May
2018
28 May
'18
2:37 p.m.
On 28 May 2018 at 06:37, Chris Robinson <chris.kcat(a)gmail.com> wrote:
Also, checking dst <= src, even with the expected results, doesn't guarantee the two memory ranges don't overlap. Aside from when dst==src, if dst = src - i and n > i, the tail of dst would overlap the head of src.
I'd also rather see this implemented on top of memmove(), but for what it's worth, the wmemcpy() implementation in the preceding patch is sufficiently naive that that kind of overlap shouldn't be an issue.