clone 625521 -1 severity 625521 grave severity -1 important reassign -1 libc6 2.13-0exp1 retitle -1 glibc: memcpy copies down on amd64 tags -1 upstream patch fixed-upstream # sorry for the noise quit
Jonathan Nieder wrote: > Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518 > which is fixed (sort of) by commit 0354e355 (2011-04-01). By the way, in principle that might be a nice commit to cherry-pick. Not sure how to do it safely, though --- backing out the amd64 optimization would hide important bugs that can cause suffering later, while applying upstream's fix would mean that apps linked against libc would use new ABI. I guess reverting glibc-2.13~215 (Improve 64bit memcpy/memmove for Atom, Core 2 and Core i7, 2010-06-30) in sid (but not experimental) and encouraging people to test libc6/experimental might be a good way. Do you know how soon upstream's planning to release 2.14? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
