| commit | 1721f0a406e52f976f9daf6f59acf42c1dbd33ff | |
| author | Siddhesh Poyarekar <siddhesh@redhat.com> | |
| Thu, 27 Nov 2014 05:45:45 +0000 (27 11:15 +0530) | ||
| committer | Siddhesh Poyarekar <siddhesh@redhat.com> | |
| Thu, 27 Nov 2014 05:45:45 +0000 (27 11:15 +0530) | ||
| tree | b298f4a2a303309f541b5a369f74b823708be8a3 | treesnapshot (tar.gz zip) |
| parent | d88548f497e52ad7633db1f3243daef0ba9fe54b | commitdiff |
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.
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.
| ChangeLog | diffblobblamehistory | |
| string/bits/string3.h | diffblobblamehistory |