This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/12518] memcpy acts randomly (and differently) with overlapping areas
- From: "tudorb at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 12 Aug 2013 17:19:54 +0000
- Subject: [Bug libc/12518] memcpy acts randomly (and differently) with overlapping areas
- Auto-submitted: auto-generated
- References: <bug-12518-131 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12518
Tudor Bosman <tudorb at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tudorb at gmail dot com
--- Comment #28 from Tudor Bosman <tudorb at gmail dot com> ---
FYI, this bug has bitten me in a different way: memcpy() copying backwards
defeats the MADV_SEQUENTIAL flag to madvise(). A trivial file copier
implementation (mmap source, mmap destination, set MADV_SEQUENTIAL, memcpy from
source to destination) would perform much worse on machines that support SSSE3
than on machines that don't because of this bug.
(Before anyone tells me that I should copy files using read() and write(), my
actual usage pattern was more complex, but the details are irrelevant.)
--
You are receiving this mail because:
You are on the CC list for the bug.