public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/25399] undefined reference to `__warn_memset_zero_len' when changing gnuc version Date: Thu, 05 Nov 2020 16:12:46 +0000 [thread overview] Message-ID: <bug-25399-131-0NiF4mNHNi@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25399-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25399 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.33 --- Comment #5 from Florian Weimer <fweimer at redhat dot com> --- Fixed by: commit dc274b141666766b8ef70992d887e3c0c5e41bed Author: Siddhesh Poyarekar <siddhesh@sourceware.org> Date: Tue Nov 3 15:09:28 2020 +0530 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. We should consider backports. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-05 16:12 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25399-131@http.sourceware.org/bugzilla/> 2020-11-05 4:44 ` siddhesh at sourceware dot org 2020-11-05 16:12 ` fweimer at redhat dot com [this message] 2021-08-25 16:36 ` ovilewade9 at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-25399-131-0NiF4mNHNi@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).