From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug backends/30251] eu-elflint is broken on LoongArch
Date: Mon, 20 Mar 2023 22:37:10 +0000 [thread overview]
Message-ID: <bug-30251-10460-keXQwZy5dp@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30251-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30251
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
CC| |mark at klomp dot org
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
Thanks, that looks perfect. Pushed as:
commit b2871fa8d430e2c5fb39e3ebc6745ea32f1bddb4
Author: Alexey Sheplyakov <asheplyakov@basealt.ru>
Date: Mon Mar 20 18:45:02 2023 +0400
LoongArch: implemented a basic machine flag check
With this patch I can use eu-elflint to verify LoongArch ELF
binaries. Previously eu-elflint was complaining about invalid
machine flags:
$ ./src/elflint --gnu-ld ./src/elflint
invalid machine flags: 0x43
$ echo $?
1
* backends/loongarch_symbol.c (loongarch_init): Hook
machine_flag_check.
* backends/loongarch_symbol.c (loongarch_machine_flag_check):
New function.
https://sourceware.org/bugzilla/show_bug.cgi?id=30251
Signed-off-by: Alexey Sheplyakov <asheplyakov@basealt.ru>
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-03-20 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 14:52 [Bug backends/30251] New: " asheplyakov at basealt dot ru
2023-03-20 22:37 ` mark at klomp dot org [this message]
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-30251-10460-keXQwZy5dp@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).