From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MGdvJ-0001yU-R9
	for qemu-devel@nongnu.org; Tue, 16 Jun 2009 15:02:21 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MGdvF-0001x1-6B
	for qemu-devel@nongnu.org; Tue, 16 Jun 2009 15:02:21 -0400
Received: from [199.232.76.173] (port=46637 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MGdvF-0001wu-1e
	for qemu-devel@nongnu.org; Tue, 16 Jun 2009 15:02:17 -0400
Received: from mail2.shareable.org ([80.68.89.115]:40129)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1MGdvE-00067A-CM
	for qemu-devel@nongnu.org; Tue, 16 Jun 2009 15:02:16 -0400
Date: Tue, 16 Jun 2009 20:02:14 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] [PATCH] ARM7TDMI emulation
Message-ID: <20090616190214.GM11893@shareable.org>
References: <200707021527.54435.uli@suse.de> <200707031645.51832.uli@suse.de>
	<5b31733c0906151211o1c95245ay38f2d09c123ea0c9@mail.gmail.com>
	<200906161825.18981.paul@codesourcery.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200906161825.18981.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paul Brook <paul@codesourcery.com>
Cc: Filip Navara <filip.navara@gmail.com>, qemu-devel@nongnu.org

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