https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61294
--- Comment #13 from Siddhesh Poyarekar <siddhesh at redhat dot com> ---
Fixed in glibc:
commit 1721f0a406e52f976f9daf6f59acf42c1dbd33ff
Author: Siddhesh Poyarekar <siddh...@redhat.com>
Date: Thu Nov 27 11:15:45 2014 +0530
Don't use __warn_memset_zero_len for gcc-5.0 or newer
gcc now warns when the arguments to memset may have been accidentally
transposed (i.e. length set to zero instead of the byte), so we don't
need that bit of the code in glibc headers anymore.
Tested on x86_64. Coe generated by gcc 4.8 is identical with or
without the patch. I also tested gcc master, which does not result in
any new failures. It does fail quite a few FORTIFY_SOURCE tests, but
those failures are not due to this patch.
