qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-arm in various flavours and circumstances
Date: Sat, 7 Aug 2004 14:11:40 +0100	[thread overview]
Message-ID: <200408071411.40868.paul@codesourcery.com> (raw)
In-Reply-To: <20040807123701.GA9762@xi.wantstofly.org>

On Saturday 07 August 2004 13:37, Lennert Buytenhek wrote:
> OK, I built a number of different ARM binaries with different toolchains,
> a few different versions of qemu, and ran them under a few different
> circumstances.
<snip>
> The results
> -----------
> bigendian:
> - The bigendian binaries (armv?eb, armv?teb) always result in
>   "Error loading $NAME_OF_BINARY", under every version of qemu
>   (I didn't muck with WORDS_BIGENDIAN.)

I haven't tried big-endian binaries. I suspect you won't be able to run both 
big and little endian binaries with the same version of qemu.

> setarch i686:
> - An FC2-compiled qemu-arm, when ran on an FC2 host without setarch i686,
>   under each and every circumstance gives a sig11.
> - An FC2-compiled qemu-arm, when ran on an FC2 host with setarch i686,
>   always behaves the same as a RH73-compiled qemu-arm when ran on an FC2
>   host.  Meaning, sometimes it works, sometimes it doesn't -- see below.

I suspect this is a generic qemu problem, not specific to qemu-arm.

> When using either a RH73-compiled qemu or setarch i686:
> - All arm-unknown-linux-gnu and armv4e-redhat-linux toolchains produce
>   binaries that work under qemu.
> - There is no difference in results between qemu 0.6.0 and qemu 20040806.
> - There is no difference in results between armv5e and armv5te binaries.
> - All armv5(t)e binaries give a sig11 under qemu 0.6.0 and qemu 20040806,
>   but under qemu 20040806 plus Paul's three patches they give sig4:
>   "qemu: uncaught target signal 4 (Illegal instruction) - exiting"

armv5 support is still incomplete, even with my patches. Thumb state, and the 
interworking branch instruction (bx) are still missing. I'm working on it 
(slowly).

A side-effect of my armv5e patch is that more illegal/unrecognised 
instructions are detected. Without the patch they are probably misinterpreted 
as a nonsensical form of a different instruction.

Paul

      reply	other threads:[~2004-08-07 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-07 12:37 [Qemu-devel] qemu-arm in various flavours and circumstances Lennert Buytenhek
2004-08-07 13:11 ` Paul Brook [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=200408071411.40868.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --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).