From: Paul Brook <paul@codesourcery.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Vincent Sanders <vince@simtec.co.uk>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Add ARM920T to ARM emulation
Date: Mon, 1 Jun 2009 13:13:48 +0100 [thread overview]
Message-ID: <200906011313.49802.paul@codesourcery.com> (raw)
In-Reply-To: <20090601113512.GA16957@shareable.org>
> I notice that ARMv4T adds the BX instruction, implying that B isn't
> able to switch to Thumb mode although it can in later architectures (I
> never saw the point in BX, and I guess ARM ended up the same :-)
>
> Is the behaviour defined to _not_ switch to Thumb when using B to an
> address with the low order bit set, or does it trap, or is it
> unpredictable?
You need to look again at the B instruction. Hopefully then you'll realise why
you're talking nonsense.
B is a direct branch that never changes mode. BX is an indirect branch that
mode switches based on the low address bit.
BL and BLX(register) are exactly the same as B/BX except they also set LR.
BLX(immediate) is a direct mode switching call.
loads into the PC either ignore(v4t) or mode switch (v5) on the low address
bit.
ALU writes to the PC always ignore the low bit in Thumb mode. In ARM mode the
low bit is either ignored(v6) or used to mode switch (v7).
BX was introduced in v4t, BLX was introduced in v5.
Paul
next prev parent reply other threads:[~2009-06-01 12:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 13:23 [Qemu-devel] Add ARM920T to ARM emulation Vincent Sanders
2009-05-29 13:23 ` [Qemu-devel] [PATCH 1/1] Update ARM emulation to be version 4t by default Vincent Sanders
2009-05-29 21:59 ` Paul Brook
2009-05-30 10:08 ` Vincent Sanders
2009-05-29 22:05 ` [Qemu-devel] Add ARM920T to ARM emulation Paul Brook
2009-06-01 11:35 ` Jamie Lokier
2009-06-01 12:13 ` Paul Brook [this message]
2009-06-01 13:29 ` Avi Kivity
2009-06-01 13:48 ` Tristan Gingold
2009-06-01 13:58 ` Avi Kivity
2009-06-01 16:34 ` Paul Brook
2009-06-01 23:11 ` Jamie Lokier
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=200906011313.49802.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
--cc=vince@simtec.co.uk \
/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).