From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Missing ARMv6 instructions?
Date: Thu, 30 Mar 2006 16:50:48 +0100 [thread overview]
Message-ID: <200603301650.49994.paul@codesourcery.com> (raw)
In-Reply-To: <20060330152524.GA29791@xi.wantstofly.org>
> Note that the new ARM ABI being pushed by ARM ltd, which is called
> EABI, mandates using a thumb-related instruction (bx) in the function
> exit path.
No it doesn't. The EABI mandates that code be interworking safe.
It's possible to implement this is an way that only uses bx when actually
returning to Thumb code, ie when you already know your hardware supports bx.
In practice many distros may assume Thumb capable hardware in the same way
many x86 distros assume at least i486 or i686, but that's an entirely
different issue.
Paul
next prev parent reply other threads:[~2006-03-30 15:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 12:33 [Qemu-devel] Missing ARMv6 instructions? Wolfgang Schildbach
2006-03-29 14:39 ` Paul Brook
2006-03-29 16:00 ` Wolfgang Schildbach
2006-03-29 20:39 ` Jamie Lokier
2006-03-29 22:01 ` Paul Brook
2006-03-29 22:36 ` John Hogerhuis
2006-03-29 22:37 ` Jamie Lokier
2006-03-30 9:22 ` Wolfgang Schildbach
2006-03-30 14:30 ` Jamie Lokier
2006-03-30 15:25 ` Lennert Buytenhek
2006-03-30 15:50 ` Paul Brook [this message]
2006-03-29 20:40 ` Jamie Lokier
2006-04-01 19:51 ` Chris Wilson
2006-04-01 20:06 ` Jonas Maebe
2006-04-02 1:26 ` Kevin F. Quinn
2006-04-02 16:32 ` Jamie Lokier
2006-04-02 16:42 ` Chris Wilson
2006-04-04 19:42 ` Daniel Jacobowitz
2006-04-05 14:41 ` Thiemo Seufer
2006-04-03 6:42 ` Karel Gardas
2006-04-03 7:00 ` M. Warner Losh
2006-04-03 12:42 ` Paul Brook
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=200603301650.49994.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).