From: Filip Navara <filip.navara@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 0/3] RFC: TCG ARM optimizations
Date: Mon, 29 Jun 2009 19:50:26 +0200 [thread overview]
Message-ID: <5b31733c0906291050w355b2fe0n9ac6f62f3486e47c@mail.gmail.com> (raw)
Hello!
I have been playing with some optimizations on the generated code for
ARM target and x86 host. The result are the following three patches
that improve the performance by 10% for Dhrystone benchmark compiled
for the ARM7TDMI target. Also the size of the output x86 code has
shrunk by up to 40% in some cases. These patches are relatively small
and self-contained, so I would like to get them to merged eventually
if others agree.
I've some ideas for further optimizations, but implementing them would
require substantial effort and the benefits are questionable.
Big thanks goes to Laurent Desnogues who actually had suggested where
the bottlenecks are.
Best regards,
Filip Navara
next reply other threads:[~2009-06-29 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 17:50 Filip Navara [this message]
2009-06-29 17:59 ` [Qemu-devel] [PATCH 0/3] RFC: TCG ARM optimizations Laurent Desnogues
2009-06-29 18:26 ` Filip Navara
2009-06-29 18:58 ` Blue Swirl
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=5b31733c0906291050w355b2fe0n9ac6f62f3486e47c@mail.gmail.com \
--to=filip.navara@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).