From: Fabrice Bellard <fabrice.bellard@free.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] gcc as a backend to generate better code
Date: Wed, 15 Oct 2003 10:18:36 +0200 [thread overview]
Message-ID: <3F8D02DC.90508@free.fr> (raw)
In-Reply-To: 20031015031622.131453eb.jrydberg@night.trouble.net
Johan Rydberg wrote:
> The TODO file states the following:
>
> - use gcc as a backend to generate better code (easy to do by using
> op-i386.c operations as local inline functions).
>
> How would this be done, actually?
The executable is launched at least once with the standard QEMU to
record translation block statistics, location and code reference (from
which file it comes, at which offset).
Then an off-line tool is launched to convert recorded translation blocks
to a .so file using gcc by generating C code from each micro operation.
When QEMU is launched again, it can scan a directory containing .so
files for all statically compiled programs. Then it can load the
corresponding .so file and use the translated blocks stored inside.
With this method, only heavily used translations blocks are compiled
with gcc. The rest is translated with QEMU.
Fabrice.
next prev parent reply other threads:[~2003-10-15 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 1:16 [Qemu-devel] gcc as a backend to generate better code Johan Rydberg
2003-10-15 8:18 ` Fabrice Bellard [this message]
2003-10-15 8:24 ` Chad Page
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=3F8D02DC.90508@free.fr \
--to=fabrice.bellard@free.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 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.