diff options
| author | Siddhesh Poyarekar <siddhesh@sourceware.org> | 2020-11-03 15:09:28 +0530 |
|---|---|---|
| committer | Siddhesh Poyarekar <siddhesh@sourceware.org> | 2020-11-05 10:02:10 +0530 |
| commit | dc274b141666766b8ef70992d887e3c0c5e41bed (patch) | |
| tree | f6c94c06251e84766a709dcf94632506fb7bc3b5 /support | |
| parent | 9a99c682144bdbd40792ebf822fe9264e0376fb5 (diff) | |
| download | glibc-dc274b141666766b8ef70992d887e3c0c5e41bed.tar.gz glibc-dc274b141666766b8ef70992d887e3c0c5e41bed.tar.xz glibc-dc274b141666766b8ef70992d887e3c0c5e41bed.zip | |
Remove __warn_memset_zero_len [BZ #25399]
Non-gcc compilers (clang and possibly other compilers that do not masquerade as gcc 5.0 or later) are unable to use __warn_memset_zero_len since the symbol is no longer available on glibc built with gcc 5.0 or later. While it was likely an oversight that caused this omission, the fact that it wasn't noticed until recently (when clang closed the gap on _FORTIFY_SUPPORT) that the symbol was missing. Given that both gcc and clang are capable of doing this check in the compiler, drop all remaining signs of __warn_memset_zero_len from glibc so that no more objects are built with this symbol in future.
Diffstat (limited to 'support')
0 files changed, 0 insertions, 0 deletions