From: Aurelien Jarno <aurelien@aurel32.net>
To: Richard Henderson <rth@twiddle.net>
Cc: TeLeMan <geleman@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] tcg/arm: improve direct jump
Date: Thu, 10 Dec 2015 19:21:19 +0100 [thread overview]
Message-ID: <20151210182119.GA25118@aurel32.net> (raw)
In-Reply-To: <56699ACD.9080009@twiddle.net>
On 2015-12-10 07:31, Richard Henderson wrote:
> On 12/10/2015 12:02 AM, Aurelien Jarno wrote:
> >Note: I don't really get the reason for the current 16MB limit. With the
> >standard branch instructions the offset is coded on 24 bits, but shifted
> >right by 2, which should give us a +/-32MB jumps, and therefore a 32MB
> >limit.
>
> That might be me with the off-by-one error on the bit counting...
While the way to store the value has been changed a few times recently,
the original value dates from this commit:
commit 1cb0661e009267a5d060c4686f0857784a8da228
Author: balrog <balrog@c046a42c-6fe2-441c-8c8c-71466251a162>
Date: Mon Dec 1 02:10:17 2008 +0000
arm: Reserve code buffer in memory range reachable for pc-relative branch.
Unfortunately this range is so narrow that I'm not sure if it makes more
sense to always use memory load to pc kind of branch instead.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5844 c046a42c-6fe2-441c-8c8c-71466251a162
This doesn't fully explain the reason why 16MB and not 32MB.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2015-12-10 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 8:02 [Qemu-devel] [PATCH] tcg/arm: improve direct jump Aurelien Jarno
2015-12-10 15:31 ` Richard Henderson
2015-12-10 18:21 ` Aurelien Jarno [this message]
2015-12-11 2:25 ` TeLeMan
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=20151210182119.GA25118@aurel32.net \
--to=aurelien@aurel32.net \
--cc=geleman@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.