From: "Laurent Desnogues" <laurent.desnogues@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] TCG new op: setcond
Date: Wed, 5 Nov 2008 17:11:43 +0100 [thread overview]
Message-ID: <761ea48b0811050811l18152234jfc3046f2a502fecf@mail.gmail.com> (raw)
In-Reply-To: <49105B1D.6080901@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Hello,
Here is an updated patch for setcond.
Changes since the previous patch:
- support TCG i386 for 32 and 64 bit variants
- support TCG x86_64 support for 32 and 64 bit variants
- fix for x86_64 prefix output
- fix for input/output overlap
- use setcond for Alpha cmp instructions
- add setcondi
Digging into x86 is certainly not a pleasant experience for me,
especially as I have no experience on it. So this patch may
contain bugs and overlooks; note however my changes were
tested on x86_64 and i386 platforms with test programs for
Alpha and ARM.
What remains to be done:
- document setcond in tcg/README
- implement it in all backends (ARM, PPC, PPC64, SPARC)
- use it at least once in every frontend (cris, i386, m68k, MIPS,
PPC, sh4, SPARC)
- provide tests.
Also there's a choice to be done between return 1 if the test
succeeds or -1.
I am concerned by 64 bit setcond on the register-started i386.
Isn't there a high risk the register allocator will run out of
registers? If it's so, I guess it should be rewritten with a helper.
Thanks to Paul and Avi for their comments and uncovering silly
bugs and overlooks.
Comments and criticisms welcome as usual :-)
Laurent
Signed-off-by: Laurent Desnogues <laurent.desnogues@gmail.com>
[-- Attachment #2: setcond-2.patch.bz2 --]
[-- Type: application/x-bzip2, Size: 3143 bytes --]
next prev parent reply other threads:[~2008-11-05 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 10:15 [Qemu-devel] [RFC] TCG new op: setcond Laurent Desnogues
2008-11-04 13:16 ` Paul Brook
2008-11-04 13:33 ` Laurent Desnogues
2008-11-04 14:24 ` Avi Kivity
2008-11-05 16:11 ` Laurent Desnogues [this message]
2008-11-09 10:50 ` Blue Swirl
-- strict thread matches above, loose matches on Subject: below --
2008-11-08 19:13 Laurent Desnogues
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=761ea48b0811050811l18152234jfc3046f2a502fecf@mail.gmail.com \
--to=laurent.desnogues@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).