about summary refs log tree commit diff
path: root/.gitignore
diff options
context:
space:
mode:
authorSiddhesh Poyarekar <siddhesh@redhat.com>2014-11-27 11:15:45 +0530
committerSiddhesh Poyarekar <siddhesh@redhat.com>2014-11-27 11:15:45 +0530
commit1721f0a406e52f976f9daf6f59acf42c1dbd33ff (patch)
treeb298f4a2a303309f541b5a369f74b823708be8a3 /.gitignore
parentd88548f497e52ad7633db1f3243daef0ba9fe54b (diff)
downloadglibc-1721f0a406e52f976f9daf6f59acf42c1dbd33ff.tar.gz
glibc-1721f0a406e52f976f9daf6f59acf42c1dbd33ff.tar.xz
glibc-1721f0a406e52f976f9daf6f59acf42c1dbd33ff.zip
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.
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions