From: Stefan Weil <weil@mail.berlios.de>
To: TeLeMan <geleman@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] tcg, tci: Add TCG and interpreter for bytecode (virtual machine)
Date: Fri, 23 Oct 2009 20:58:05 +0200 [thread overview]
Message-ID: <4AE1FCBD.8030904@mail.berlios.de> (raw)
In-Reply-To: <a38b25540910221831u1f43a337s8863b93930f275e9@mail.gmail.com>
TeLeMan schrieb:
> Tested i386-softmmu only. Now tci can run windows xp sp2 and its speed
> is about 6 times slower than jit.
> --
> SUN OF A BEACH
Great. Many thanks for the fixes, enhancements and for the testing, too.
Is patch 4 (call handling) needed, or is it an optimization?
If it is needed, the tcg disassembler has to be extended as well.
And did patch 5 (inline) speed up the code? I had expected
that static functions don't need inline, because the compiler
can optimize them anyway.
Regards,
Stefan
next prev parent reply other threads:[~2009-10-23 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 1:31 [Qemu-devel] Re: [PATCH] tcg, tci: Add TCG and interpreter for bytecode (virtual machine) TeLeMan
2009-10-23 18:58 ` Stefan Weil [this message]
2009-10-24 3:23 ` TeLeMan
2009-10-26 19:08 ` Stuart Brady
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=4AE1FCBD.8030904@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=geleman@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).