From: Aurelien Jarno <aurelien@aurel32.net>
To: Richard Henderson <rth@twiddle.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] mips setcond and movcond
Date: Sun, 20 Dec 2009 00:03:31 +0100 [thread overview]
Message-ID: <20091219230331.GV24729@hall.aurel32.net> (raw)
In-Reply-To: <cover.1261260692.git.rth@twiddle.net>
On Sat, Dec 19, 2009 at 10:43:31PM +0000, Richard Henderson wrote:
> It has been compile tested, but nothing else.
>
> I'm moderately surprised at the implementation of brcond. It's
> missing the BLTZ, BLEZ, BGTZ, BGEZ branches. It's could be
> improved with the SLTI and SLTIU insns used here with setcond.
The MIPS TCG support is really new, and the goal was to make it working,
not to get it as optimized as possible. Anyway I doubt it will make a
big difference in speed.
> Indeed, I suspect that a good implementation of brcond would be
> to take care of the cases implementable directly by branches,
> and then call into setcond to take care of the rest. I don't
> plan to do that.
>
>
> r~
>
>
>
> Richard Henderson (3):
> tcg: Add tcg_swap_cond.
> tcg-mips: Implement setcond, setcond2.
> tcg-mips: Implement movcond.
>
> tcg/mips/tcg-target.c | 296 ++++++++++++++++++++++++++++++++++++++++++++++++-
> tcg/tcg.h | 8 ++
> 2 files changed, 302 insertions(+), 2 deletions(-)
>
>
>
>
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2009-12-19 23:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 22:32 [Qemu-devel] [PATCH 0/3] mips setcond and movcond Richard Henderson
2009-12-19 22:32 ` [Qemu-devel] [PATCH 1/3] tcg: Add tcg_swap_cond Richard Henderson
2009-12-19 22:32 ` [Qemu-devel] [PATCH 2/3] tcg-mips: Implement setcond, setcond2 Richard Henderson
2009-12-20 0:00 ` Aurelien Jarno
2009-12-19 22:32 ` [Qemu-devel] [PATCH 3/3] tcg-mips: Implement movcond Richard Henderson
2009-12-19 23:03 ` Aurelien Jarno [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=20091219230331.GV24729@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.