From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 1263747 <1263747@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1263747] Re: Arm64 fails to run a binary which runs OK on real hardware
Date: Mon, 23 Dec 2013 22:19:55 +0000 [thread overview]
Message-ID: <CAFEAcA-uWgEYPopqhLizQxOYkpfHR0Jsr5Y1FbK7SFzSt9u93A@mail.gmail.com> (raw)
In-Reply-To: <20131223212721.26965.9817.malone@soybean.canonical.com>
On 23 December 2013 21:27, Richard Jones <rjones@redhat.com> wrote:
> It's an Aarch64 binary so it won't run on 32 bit ARM at all. However I
> guess you meant does the equivalent program run on 32 bit ARM, and the
> answer is yes, but that doesn't tell us much because OCaml uses separate
> code generators for 32 and 64 bit ARM.
Yes, that's why I said "equivalent binary". It's a useful check because it
can tell us whether the program is using things our linux-user emulation
doesn't get right at all (examples: multiple threads; some interactions of
signals and blocking syscalls); so it divides the bug into "probably in
linux-user" vs "probably a target-arm bug".
I see you've tracked the issue down in this case, though.
thanks
-- PMM
next prev parent reply other threads:[~2013-12-23 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 18:38 [Qemu-devel] [Bug 1263747] [NEW] Arm64 fails to run a binary which runs OK on real hardware Richard Jones
2013-12-23 20:13 ` Peter Maydell
2013-12-23 21:27 ` [Qemu-devel] [Bug 1263747] " Richard Jones
2013-12-23 22:19 ` Peter Maydell [this message]
2013-12-23 21:51 ` Richard Jones
2013-12-23 22:03 ` Richard Jones
2014-01-25 2:03 ` sumanth
2016-06-27 21:20 ` T. Huth
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=CAFEAcA-uWgEYPopqhLizQxOYkpfHR0Jsr5Y1FbK7SFzSt9u93A@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=1263747@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).