From: Andreas Schwab <schwab@suse.de>
To: Thomas Huth <huth@tuxfamily.org>
Cc: qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>,
Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH] qemu-binfmt-conf.sh: Fix m68k_mask
Date: Wed, 22 Mar 2017 13:04:12 +0100 [thread overview]
Message-ID: <mvmo9wtsekj.fsf@suse.de> (raw)
In-Reply-To: <a7886994-b4fe-3c6c-40ee-213b36e1e4b4@tuxfamily.org> (Thomas Huth's message of "Wed, 22 Mar 2017 12:46:56 +0100")
On Mär 22 2017, Thomas Huth <huth@tuxfamily.org> wrote:
> On 21.03.2017 10:38, Andreas Schwab wrote:
>> The m68k mask should not remove the low bit of the ELF version field and
>> should ignore the OS/ABI field.
>
> Did you encounter a problem with a real binary here?
Yes, some binaries are using ELFOSABI_GNU instead of ELFOSABI_SYSV. All
other patterns already ignore the OS/ABI field.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2017-03-22 12:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 9:38 [Qemu-devel] [PATCH] qemu-binfmt-conf.sh: Fix m68k_mask Andreas Schwab
2017-03-22 11:46 ` Thomas Huth
2017-03-22 12:04 ` Andreas Schwab [this message]
2017-03-22 12:12 ` Laurent Vivier
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=mvmo9wtsekj.fsf@suse.de \
--to=schwab@suse.de \
--cc=huth@tuxfamily.org \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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 NNTP newsgroup(s).