From: Filip Navara <filip.navara@gmail.com>
To: Pablo Virolainen <Pablo.Virolainen@nomovok.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] RFC: TCG constant propagation.
Date: Wed, 5 Aug 2009 10:48:05 +0200 [thread overview]
Message-ID: <5b31733c0908050148m512aa221p70ba8b3e56699203@mail.gmail.com> (raw)
In-Reply-To: <4A793F32.4090207@nomovok.com>
On Wed, Aug 5, 2009 at 10:13 AM, Pablo
Virolainen<Pablo.Virolainen@nomovok.com> wrote:
> Filip Navara kirjoitti:
>>
>> Add support for constant propagation to TCG. This has to be paired with
>> the liveness
>> analysis to remove the dead code. Not all possible operations are covered,
>> but the
>> most common ones are. This improves the code generation for several ARM
>> instructions,
>> like MVN (immediate), and it may help other targets as well.
>
> On my small benchmark, qemu-system-sh4 was about 3% slower on Intel Xeon
> E5405@2.00GHz. I'm running 64-bit mode. My mini benchmark is to build zlib
> 1.2.3, so it's 'real' world work load. Ran the benchmark several times and
> results seems to be pretty constant.
Thanks for testing and reporting the results. I'll see if I can reduce
the overhead or if I should ditch the patch.
> ps. I added INDEX_op_*_i64 cases to the evaluation part. I'm not completly
> sure if those &mask should be there.
I've rewritten the patch and fixed the 64-bit mess that was there. It
is available at
http://repo.or.cz/w/qemu/navara.git?a=commit;h=5df3a524fc0b923cf2e5e1883ff550d055d36eb5
Best regards,
Filip Navara
prev parent reply other threads:[~2009-08-05 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 14:37 [Qemu-devel] [PATCH] RFC: TCG constant propagation Filip Navara
2009-07-23 9:08 ` Filip Navara
2009-07-23 9:25 ` Laurent Desnogues
2009-07-23 9:30 ` Paul Brook
2009-07-23 9:49 ` Filip Navara
2009-07-23 20:10 ` Stuart Brady
2009-07-23 20:28 ` Filip Navara
2009-07-23 22:02 ` Daniel Jacobowitz
2009-08-05 8:13 ` Pablo Virolainen
2009-08-05 8:48 ` Filip Navara [this message]
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=5b31733c0908050148m512aa221p70ba8b3e56699203@mail.gmail.com \
--to=filip.navara@gmail.com \
--cc=Pablo.Virolainen@nomovok.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).