From: "John R. Hogerhuis" <jhoger@pobox.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu optimization
Date: Tue, 30 Aug 2005 11:05:40 -0700 [thread overview]
Message-ID: <1125425140.3983.29.camel@aragorn> (raw)
In-Reply-To: <200508301217.40302.paul@codesourcery.com>
On Tue, 2005-08-30 at 12:17 +0100, Paul Brook wrote:
> You might want to look at my hand-coded backed for qemu. The intention is that
> this will eventually replace dyngen/gcc altogether. Currently everything
> except the experimental m68k target uses a mixture of the old and the
> micro-ops.
>
Handwritten code generators are definitely the future for QEMU, at least
where virtualization doesn't make sense (host and guest CPU don't match,
or when you don't have root or admin access to the host).
> One of the differences is that most of the semantics and guest CPU state
> accesses are explicit, so it should be possible to use conventional
> optimisation techniques (including peepholes).
>
> Source and patches can be found at
> https://nowt.dyndns.org
>
> As proof-of-concept I also implemented a simple register propagation pass, and
> got a 15% speedup on the nbench benchmark.
>
> Paul
>
>
I just downloaded the patched tree off your page. Tried to build it
(./configure && make) compiling on Debian GNU/Linux, gcc version 3.3 but
no-workey.
Any idea what I'm doing wrong (I haven't given it a hard look yet)?
(last line of build, let me know if you need more).
gcc -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I.
-I/home/john/projects/qemu/target-mips -I/home/john/projects/qemu
-I/home/john/projects/qemu/host-i386 -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-I/home/john/projects/qemu/fpu -I/home/john/projects/qemu/slirp -c -o
translate-all.o /home/john/projects/qemu/translate-all.c
/home/john/projects/qemu/translate-all.c: In function
`cpu_restore_state':
/home/john/projects/qemu/translate-all.c:1496: error: `CC_OP_DYNAMIC'
undeclared (first use in this function)
/home/john/projects/qemu/translate-all.c:1496: error: (Each undeclared
identifier is reported only once
/home/john/projects/qemu/translate-all.c:1496: error: for each function
it appears in.)
/home/john/projects/qemu/translate-all.c:1497: error: structure has no
member named `cc_op'
make[1]: *** [translate-all.o] Error 1
make[1]: Leaving directory `/home/john/projects/qemu/mips-softmmu'
make: *** [all] Error 1
~/projects/qemu :(
next prev parent reply other threads:[~2005-08-30 18:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 16:56 [Qemu-devel] Re: qemu 0.7.1 + dkms-qvm86-0.7.1 (mandriva 2005 / cooker) produces version mismatch Hannes Fuchs
2005-08-29 18:05 ` [Qemu-devel] QEMU_TMPDIR temp folder for KQEMU for Windows Francois Rioux
2005-08-29 18:53 ` John R. Hogerhuis
2005-08-29 21:59 ` Jim C. Brown
2005-08-30 7:29 ` [Qemu-devel] qemu optimization John R. Hogerhuis
2005-08-30 11:17 ` Paul Brook
2005-08-30 18:05 ` John R. Hogerhuis [this message]
2005-08-30 18:30 ` Paul Brook
2005-08-29 22:01 ` [Qemu-devel] QEMU_TMPDIR temp folder for KQEMU for Windows Jim C. Brown
2005-08-30 3:45 ` Francois Rioux
2005-08-30 9:08 ` Filip Navara
2005-08-30 13:42 ` Francois Rioux
2005-08-30 14:02 ` Paul Brook
2005-09-03 13:51 ` ace
2005-09-03 17:35 ` Doctor Bill
2005-09-03 14:48 ` Filip Navara
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=1125425140.3983.29.camel@aragorn \
--to=jhoger@pobox.com \
--cc=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).