https://bugs.freedesktop.org/show_bug.cgi?id=107670
--- Comment #2 from [email protected] ---
(In reply to Timothy Arceri from comment #1)
> There already is asm optimized version of memcpy() in glibc. Why would we
> want to reinvent that in Mesa?
>
> glibc should pick the right implementation for you system.
Because some implementations copy data backwards and this creates a huge
problem when it is written over PCIe.
To be clear:
for(i=0;i<size;i++) dst[i]=src[i]; // forward copy.
for(i=size-1;i>=0;i--) dst[i]=src[i]; // backwards copy
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
