From: Nick Clifton <nickc@redhat.com>
To: Tom Kacvinsky <tkacvins@gmail.com>, Binutils <binutils@sourceware.org>
Subject: Re: request for enhancement in BFD and gold linkers in regards to .comment section
Date: Wed, 1 Mar 2023 13:41:22 +0000 [thread overview]
Message-ID: <3ef565e0-011e-1ffd-cac6-04aa8f371537@redhat.com> (raw)
In-Reply-To: <CAG_eJLdR1WSrLhuoF0OoFZNwRkMzy6iPLgXD442CHEFP=KvvLw@mail.gmail.com>
Hi Tom,
> I have noticed that the LLVM linker will add something to the .comment
> section of binaries it produces for the version of lld used to produce an
> ELF executable or shared library.
Does it ? I do not see this:
% clang hello.c
% readelf -p.comment a.out
String dump of section '.comment':
[ 0] GCC: (GNU) 12.2.1 20221121 (Red Hat 12.2.1-4)
[ 2e] GCC: (GNU) 12.0.1 20220413 (Red Hat 12.0.1-0)
[ 5c] clang version 14.0.5 (Fedora 14.0.5-2.fc36)
So there is a note for the version of Clang, but not one for the version of lld.
Maybe this is a new feature ? I am using clang/llvm/lld version 14.0.5.
> For the gold liker, I see I can do a readelf -p .note.gnu.gold-version and
> get the version of gold used to make an ELF file.
Again I do not see this:
% gcc hello.c -fuse-ld=gold
% readelf -p.comment a.out
String dump of section '.comment':
[ 1] GCC: (GNU) 12.2.1 20221121 (Red Hat 12.2.1-4)
[ 2f] GCC: (GNU) 12.0.1 20220413 (Red Hat 12.0.1-0)
> I see nothing similar for the BFD linker.
True - this feature is not currently supported.
> So the request for enhancement is to add something to the .comment section
> as to which version of the BFD or gold linker was used to produce the ELF.
>
> I can file a BZ if that is the preferred way of receiving a request such as
> this.
It is, so please do file a BZ. If you can include a reproducer that would help.
Cheers
Nick
next prev parent reply other threads:[~2023-03-01 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 12:58 Tom Kacvinsky
2023-03-01 13:41 ` Nick Clifton [this message]
2023-03-01 14:53 ` Tom Kacvinsky
2023-03-01 15:15 ` Tom Kacvinsky
2023-03-19 20:36 ` Tom Kacvinsky
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=3ef565e0-011e-1ffd-cac6-04aa8f371537@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=tkacvins@gmail.com \
/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).