From: Nick Clifton <nickc@redhat.com>
To: Jeff Law <jeffreyalaw@gmail.com>, binutils@sourceware.org
Subject: Re: RFC: readelf: Explain why LLVM bitcode files cannot be read
Date: Mon, 22 Aug 2022 11:18:09 +0100 [thread overview]
Message-ID: <182cb64a-b37f-4157-2fa2-bd725d5cff26@redhat.com> (raw)
In-Reply-To: <7d833071-ab40-4ac5-2f4e-865afd0d294f@gmail.com>
Hi Jeff,
> I think the same issue arises with golang -- its .o files are not ELF, but can be read by the golang variants of objdump, nm, etc. So you might want to look at doing
> something similar for golang as well.
A great idea. I have recoded the patch to create a new function
which checks the magic number, and if it is not ELF then it tests
for LLVM bitcode files and golang object files. This time I have
put the magic numbers into a static array, so it should be easy to
add more sequences should we wish to do so.
Cheers
Nick
next prev parent reply other threads:[~2022-08-22 10:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 14:20 Nick Clifton
2022-08-19 16:06 ` Jeff Law
2022-08-22 10:18 ` Nick Clifton [this message]
2022-08-23 15:26 ` Richard Earnshaw
2022-08-23 15:30 ` Nick Clifton
2022-08-23 20:35 ` Luis Machado
2022-08-24 9:24 ` Nick Clifton
2022-08-24 10:18 ` Luis Machado
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=182cb64a-b37f-4157-2fa2-bd725d5cff26@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=jeffreyalaw@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).