From: "Martin Liška" <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] lto-plugin: update comments - remove hardwired gold
Date: Tue, 1 Mar 2022 16:41:58 +0100 [thread overview]
Message-ID: <366d051e-66f1-1abe-e0dc-de0496ab9366@suse.cz> (raw)
Pushed to master as obvious. Right now, there are 3 linkers that
can utilize the plug-in, not only gold.
Martin
lto-plugin/ChangeLog:
* lto-plugin.c (process_offload_section): Use a linker as many
comments are connected to gold linker.
(process_option): Likewise.
---
lto-plugin/lto-plugin.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/lto-plugin/lto-plugin.c b/lto-plugin/lto-plugin.c
index c9c048d3631..593fbc91383 100644
--- a/lto-plugin/lto-plugin.c
+++ b/lto-plugin/lto-plugin.c
@@ -1,4 +1,4 @@
-/* LTO plugin for gold and/or GNU ld.
+/* LTO plugin for linkers like gold, GNU ld or mold.
Copyright (C) 2009-2022 Free Software Foundation, Inc.
Contributed by Rafael Avila de Espindola (espindola@google.com).
@@ -16,11 +16,11 @@ You should have received a copy of the GNU General Public License
along with this program; see the file COPYING3. If not see
<http://www.gnu.org/licenses/>. */
-/* The plugin has only one external function: onload. Gold passes it an array of
- function that the plugin uses to communicate back to gold.
+/* The plugin has only one external function: onload. A linker passes it an array of
+ function that the plugin uses to communicate back to the linker.
- With the functions provided by gold, the plugin can be notified when
- gold first analyzes a file and pass a symbol table back to gold. The plugin
+ With the functions provided by the linker, the plugin can be notified when
+ the linker first analyzes a file and pass a symbol table back to the linker. The plugin
is also notified when all symbols have been read and it is time to generate
machine code for the necessary symbols.
@@ -1139,7 +1139,7 @@ process_offload_section (void *data, const char *name, off_t offset, off_t len)
return 1;
}
-/* Callback used by gold to check if the plugin will claim FILE. Writes
+/* Callback used by a linker to check if the plugin will claim FILE. Writes
the result in CLAIMED. */
static enum ld_plugin_status
@@ -1374,7 +1374,7 @@ process_option (const char *option)
verbose = verbose || debug;
}
-/* Called by gold after loading the plugin. TV is the transfer vector. */
+/* Called by a linker after loading the plugin. TV is the transfer vector. */
enum ld_plugin_status
onload (struct ld_plugin_tv *tv)
--
2.35.1
reply other threads:[~2022-03-01 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=366d051e-66f1-1abe-e0dc-de0496ab9366@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.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).