From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Laurent Desnogues <laurent.desnogues@gmail.com>
Subject: Re: [Qemu-devel] [RFC] TCG new op: setcond
Date: Tue, 4 Nov 2008 14:16:38 +0100 [thread overview]
Message-ID: <200811041316.39122.paul@codesourcery.com> (raw)
In-Reply-To: <761ea48b0811040215l3fa16cd6j41e7ee750602e6ea@mail.gmail.com>
> this patch implements a new TCG op, setcond, that sets a temp
> to 1 if the condition is true, else to 0. The benefit is the potential
> removal of brcond instructions, and helpers size reduction which
> can lead to using TCG instead of helpers.
> - a variant that sets -1 instead of 1 for masking
I'm worried about this. If we're not careful we'll end up with an explosion of
different patterns, many of which aren't optimal of different hosts.
> - 64 bit setcond's
You should do this sooner rather than later, and on a 32-bit host.
> + /* clear ret since setcc only sets the lower 8 bits */
> + tcg_out_modrm(s, 0x01 | (ARITH_XOR << 3) | rexw, ret, ret);
This is broken. Inputs and outputs may overlap.
> + // TODO this should use tcg_out_modrm
> + // however currently tcg_out_modrm outputs an extra byte for
> [abcd]l + //tcg_out_modrm(s, (0x90 + tcg_cond_to_jcc[cond]) | P_EXT |
> P_REXB, ret, 0)
This is the wrong way to fix this. If you really care about the extra code
byte (which is harmless) you should fix tcg_out_modrm.
Also, please use C comments, not c++ style //.
Paul
next prev parent reply other threads:[~2008-11-04 13:18 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 [this message]
2008-11-04 13:33 ` Laurent Desnogues
2008-11-04 14:24 ` Avi Kivity
2008-11-05 16:11 ` Laurent Desnogues
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=200811041316.39122.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=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).