From: Laurent Desnogues <laurent.desnogues@wanadoo.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu vs gcc4
Date: Tue, 31 Oct 2006 23:31:04 +0100 [thread overview]
Message-ID: <4547CEA8.9040903@wanadoo.fr> (raw)
In-Reply-To: <200610312208.20278.paul@codesourcery.com>
Paul Brook a écrit :
> Replacing the pregenerated blocks with hand written assembly isn't feasible.
> Each target has its own set of ops, and each host would need its own assembly
> implementation of those ops. Multiply 11 targets by 11 hosts and you get a
> unmaintainable mess :-)
Shouldn't you have 11+11 and not 11*11, given your intermediate
representation? And of these 11+11, 11 have to be written
anyway (target). Or did I miss something?
> On RISC targets like ARM most instructions don't set the condition codes, so
> we don't bother doing this.
Except for ARM Thumb ISA which always sets flags. ARM is a bad
RISC example :)
I was wondering if you did some profiling to know how much time
is spent in disas_arm_insn. Of course the profiling results
would be very different for a Linux boot or a synthetic benchmark
(which makes me think that you don't support MMU, do you?).
There is a very nice trick to speed up decoding of ARM
instructions: pick up bits 20-27 and 4-7 and you (almost) get
one instruction per case entry; of course this means using a
generator to write the 4096 entries, but the result was good for
my interpreted ISS, reaching 44 M i/s on an Opteron @2.4GHz
without any compiler dependent trick (such as gcc jump to labels).
Laurent
next prev parent reply other threads:[~2006-10-31 22:29 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 18:53 [Qemu-devel] qemu vs gcc4 K. Richard Pixley
2006-10-22 22:06 ` Johannes Schindelin
2006-10-23 8:16 ` Martin Guy
2006-10-23 12:20 ` Paul Brook
2006-10-23 13:59 ` Avi Kivity
2006-10-23 14:10 ` Paul Brook
2006-10-23 14:28 ` Avi Kivity
2006-10-23 14:31 ` Paul Brook
2006-10-23 14:35 ` Avi Kivity
2006-10-23 17:41 ` K. Richard Pixley
2006-10-23 17:58 ` Paul Brook
2006-10-23 18:04 ` K. Richard Pixley
2006-10-23 18:20 ` Laurent Desnogues
2006-10-23 18:37 ` Paul Brook
2006-10-24 23:39 ` Rob Landley
2006-10-25 0:24 ` Paul Brook
2006-10-25 19:39 ` Rob Landley
2006-10-26 18:09 ` Daniel Jacobowitz
2006-10-31 16:53 ` Rob Landley
2006-10-31 19:02 ` Paul Brook
2006-10-31 20:41 ` Rob Landley
2006-10-31 22:08 ` Paul Brook
2006-10-31 22:31 ` Laurent Desnogues [this message]
2006-10-31 23:00 ` Paul Brook
2006-11-01 0:00 ` Rob Landley
2006-11-01 0:29 ` Paul Brook
2006-11-01 1:51 ` Rob Landley
2006-11-01 3:22 ` Paul Brook
2006-11-01 16:34 ` Rob Landley
2006-11-01 17:01 ` Paul Brook
2006-10-31 23:17 ` Rob Landley
2006-11-01 0:01 ` Paul Brook
2006-10-30 4:35 ` Rob Landley
2006-10-30 14:56 ` Paul Brook
2006-10-30 16:31 ` Rob Landley
2006-10-30 16:50 ` Paul Brook
2006-10-30 22:54 ` Stephen Torri
2006-10-30 23:13 ` Paul Brook
2006-10-23 1:27 ` Rob Landley
2006-10-23 1:44 ` Paul Brook
2006-10-23 1:45 ` Johannes Schindelin
2006-10-23 17:53 ` K. Richard Pixley
2006-10-23 18:08 ` Rob Landley
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=4547CEA8.9040903@wanadoo.fr \
--to=laurent.desnogues@wanadoo.fr \
--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).