From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] Fix: symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
Date: Tue, 21 Nov 2023 11:31:00 +0000 (GMT) [thread overview]
Message-ID: <20231121113100.C1B363858D33@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1367eeec2cbd1bb14b89030e199d06fc676ffc49
commit 1367eeec2cbd1bb14b89030e199d06fc676ffc49
Author: Nick Clifton <nickc@redhat.com>
Date: Tue Nov 21 11:30:03 2023 +0000
Fix: symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
PR 31067
Fix typo in previous delta: defined -> referenced.
Diff:
---
ld/ld.texi | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/ld/ld.texi b/ld/ld.texi
index 0704eece8d6..7ee06a71744 100644
--- a/ld/ld.texi
+++ b/ld/ld.texi
@@ -7547,12 +7547,12 @@ garbage collection or orphan handling.
The contents of any section whoes name starts with the prefix
@samp{.gnu.warning.} and then finishes with the name of a symbol is
treated in a similar fashion to the @samp{.gnu.warning} section, but
-only if the named symbol is defined. So for example the contents of a
-section called @samp{.gnu.warning.foo} will be displayed as warning
-message if, and only if, the symbol @samp{foo} is defined by one or
-more of the input files. This includes object files pulled in from
-static libraries, shared objects needed to complete the link and so
-on.
+only if the named symbol is referenced. So for example the contents
+of a section called @samp{.gnu.warning.foo} will be displayed as
+warning message if, and only if, the symbol @samp{foo} is referenced
+by one or more of the input files. This includes object files pulled
+in from static libraries, shared objects needed to complete the link
+and so on.
Note - because these warning messages are generated before the linker
performs garbage collection (if enabled) it is possible for a warning
next reply other threads:[~2023-11-21 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 11:31 Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 9:27 Nick Clifton
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=20231121113100.C1B363858D33@sourceware.org \
--to=nickc@sourceware.org \
--cc=bfd-cvs@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: link
Be 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).