From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: branches are expensive
Date: Thu, 19 Mar 2009 12:52:41 +0200 [thread overview]
Message-ID: <49C223F9.8030505@redhat.com> (raw)
In-Reply-To: <gpt5ht$utu$1@ger.gmane.org>
Steffen Liebergeld wrote:
> I've tested Qemu 0.10.0 and with i386-softmmu on a i386 host I get the
> following numbers:
> direct jump count 70%, 2 jumps 54%
>
> For qemu-system-arm on an ARM host, the numbers look like this:
> direct jump count 47%, 2 jumps 40%
>
> For completeness I tested qemu-system-arm on a i386 host as well:
> direct jump count 44%, 2 jumps 37%
>
> So it looks like the chaining on ARM targets is not as effective as on i386
> targets (regardless of the guest, I used the same guest setup, compiled for
> different architectures, on all tests). Do you have any ideas why this is the
> case?
>
I'd guess that predicated instructions are heavily used on ARM for
if/else sequences, so intra-page branches would be less frequent.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-19 10:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 11:05 [Qemu-devel] branches are expensive Steffen Liebergeld
2009-03-17 11:18 ` Avi Kivity
2009-03-17 11:32 ` [Qemu-devel] " Jan Kiszka
2009-03-17 12:31 ` Steffen Liebergeld
2009-03-17 12:51 ` Paul Brook
2009-03-17 13:24 ` Avi Kivity
2009-03-19 10:07 ` Steffen Liebergeld
2009-03-19 10:30 ` Laurent Desnogues
2009-03-19 10:39 ` Steffen Liebergeld
2009-03-19 11:06 ` Laurent Desnogues
2009-03-19 10:52 ` Avi Kivity [this message]
2009-03-19 11:34 ` Paul Brook
2009-03-17 11:36 ` Steffen Liebergeld
2009-03-17 13:30 ` [Qemu-devel] " Laurent Desnogues
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=49C223F9.8030505@redhat.com \
--to=avi@redhat.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 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.