From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Dynamic condition code calculation for Sparc
Date: Sun, 10 May 2009 12:07:43 +0300 [thread overview]
Message-ID: <f43fc5580905100207m144621e2t79526c1585b94ac0@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Hi,
I just committed a patch series, which implement dynamic condition
code calculation for Sparc, much like x86. The speedup for Sparc64 is
clearly visible, less so for Sparc32.
The attached follow-on optimization patches implement leaner carry
calculation and calculating the (annulled) branch brcond directly from
comparison sources, but currently they cause breakage.
Also the normal branches should be converted to calculate the brcond
directly, but this fails if the branch delay slot contains an
instruction that changes the flags. I had some code for this but had
to scratch it. Any suggestions welcome.
[-- Attachment #2: 0001-Branch-optimization-BROKEN.patch --]
[-- Type: application/mbox, Size: 4403 bytes --]
[-- Attachment #3: 0001-Convert-C-flag-input-BROKEN.patch --]
[-- Type: application/mbox, Size: 5476 bytes --]
reply other threads:[~2009-05-10 9:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f43fc5580905100207m144621e2t79526c1585b94ac0@mail.gmail.com \
--to=blauwirbel@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).