From: Jamie Lokier <jamie@shareable.org>
To: Paul Brook <paul@codesourcery.com>
Cc: Filip Navara <filip.navara@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ARM7TDMI emulation
Date: Tue, 16 Jun 2009 20:02:14 +0100 [thread overview]
Message-ID: <20090616190214.GM11893@shareable.org> (raw)
In-Reply-To: <200906161825.18981.paul@codesourcery.com>
Paul Brook wrote:
> > this is a rewritten version of the original patch to work on the latest
> > qemu git. Anything that needs to be done to get this merged?
>
> You're missing quite a few bits here. For example load pc should do the same
> as pop pc, and there are many other instructions that aren't valid on
> v5t/v5te. See the recent arm920t patches (and corresponding discussion).
I'm thinking of adding ARMv4 (not v4T) support, so I can test that
code needing to run on a real ARMv4 does not accidentally have any
unsupported instructions.
While looking into that, I found it quite difficult to find which
instructions are supported by different ARM architecture levels, and
especially how PC is treated by different instructions on the
different architectures.
Do you know of a good summary reference which lists which instructions
are available in each ARM architecture level from ARMv4 up to ARMv7
and it's variants?
(Preferably without an ARM licensing agreement or NDA).
-- Jamie
next prev parent reply other threads:[~2009-06-16 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 13:27 [Qemu-devel] [PATCH] ARM7TDMI emulation Ulrich Hecht
2007-07-02 13:40 ` Paul Brook
2007-07-02 16:14 ` Ulrich Hecht
2007-07-03 14:45 ` Ulrich Hecht
2009-06-15 19:11 ` Filip Navara
2009-06-16 17:25 ` Paul Brook
2009-06-16 19:02 ` Jamie Lokier [this message]
2009-06-16 19:05 ` Paul Brook
2009-06-16 20:49 ` Filip Navara
2009-06-16 21:47 ` Filip Navara
2009-06-17 9:55 ` Filip Navara
2009-06-17 10:24 ` Filip Navara
-- strict thread matches above, loose matches on Subject: below --
2009-07-15 12:08 Filip Navara
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=20090616190214.GM11893@shareable.org \
--to=jamie@shareable.org \
--cc=filip.navara@gmail.com \
--cc=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).