From: Christian MICHON <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Hand written code generator #2
Date: Thu, 2 Jun 2005 12:53:10 +0200 [thread overview]
Message-ID: <46d6db6605060203536fd32a71@mail.gmail.com> (raw)
In-Reply-To: <200505311623.28508.paul@codesourcery.com>
Paul,
on mingw32/x86-XP host, I see no difference on benchs with i386-softmmu.
You mentionned around 30% improvements. Any special compiler flags to
use, or compiler version?
I applied the patch on a fresh 0.7.0 version.
Christian
On 5/31/05, Paul Brook <paul@codesourcery.com> wrote:
> I've made available a new version of my hand-written code generator for qemu.
> The patch is getting rather large, so I've put it on a web server to avoid
> spamming the list:
> https://nowt.dyndns.org/patch.qemu_qop.gz
>
> In principle it's very similar to the previous patch. The main difference is
> that it now supports all target architectures, including 64-bit targets.
>
next prev parent reply other threads:[~2005-06-02 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 15:23 [Qemu-devel] Hand written code generator #2 Paul Brook
2005-06-01 5:40 ` Jens Arm
2005-06-01 9:53 ` Herbert Poetzl
2005-06-01 12:36 ` Paul Brook
2005-06-02 10:53 ` Christian MICHON [this message]
2005-06-02 13:31 ` Paul Brook
2005-06-02 13:36 ` Christian MICHON
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=46d6db6605060203536fd32a71@mail.gmail.com \
--to=christian.michon@gmail.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).