glibc

Tree: 1469f46696

Siddhesh Poyarekar 1721f0a406 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.	12 years ago
..
string2.h	Update feature guard for strdup/strndup in <bits/string2.h>	12 years ago
string3.h	Don't use __warn_memset_zero_len for gcc-5.0 or newer	12 years ago

Siddhesh Poyarekar 1721f0a406 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.

12 years ago

string2.h

Update feature guard for strdup/strndup in <bits/string2.h>

12 years ago

string3.h

Don't use __warn_memset_zero_len for gcc-5.0 or newer

12 years ago