public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Alexey Sheplyakov <>
Subject: Re: [PATCH] LoongArch: implemented a basic machine flag check
Date: Mon, 20 Mar 2023 23:35:53 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Alexey,

On Mon, Mar 20, 2023 at 06:45:02PM +0400, Alexey Sheplyakov wrote:
> 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

Thanks. I quickly peeked at the LoongArch ELF ABI specification and
this is precisely what needs to be checked.

Added a ChangeLog entry to the commit message, a reference to the
bug you filed and pushed.



      reply	other threads:[~2023-03-20 22:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 14:45 Alexey Sheplyakov
2023-03-20 22:35 ` Mark Wielaard [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).