From: Nathan Froyd <froydnj@codesourcery.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 9/9] Implement new logical instructions for ppc64
Date: Wed, 22 Apr 2009 07:02:13 -0700 [thread overview]
Message-ID: <20090422140212.GQ22588@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0904221743120.2171@linmac.oyster.ru>
On Wed, Apr 22, 2009 at 05:44:00PM +0400, malc wrote:
> On Tue, 21 Apr 2009, Nathan Froyd wrote:
> > tcg/ppc64/tcg-target.c | 36 ++++++++++++++++++++++++++++++++++++
> > tcg/ppc64/tcg-target.h | 10 ++++++++++
> > 2 files changed, 46 insertions(+), 0 deletions(-)
>
> Have you measured the speed impact of this, if so how?
I have not.
-Nathan
prev parent reply other threads:[~2009-04-22 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 1:12 [Qemu-devel] [PATCH 0/9] tcg: improve logical op support for ppc hosts, v2 Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 1/9] Add TCG ops for various logical operations Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 2/9] specialize tcg_gen_not_i64 for 32-bit targets Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 3/9] implement specialized andc_i{32,64} Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 4/9] implement specialized eqv_{i32,i64} Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 5/9] implement specialized nand_i{32,64} Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 6/9] implement specialized nor_i{32,64} Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 7/9] implement specialized orc_i{32,64} Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 8/9] Implement new logical instructions for ppc Nathan Froyd
2009-04-22 1:12 ` [Qemu-devel] [PATCH 9/9] Implement new logical instructions for ppc64 Nathan Froyd
2009-04-22 13:44 ` malc
2009-04-22 14:02 ` Nathan Froyd [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=20090422140212.GQ22588@codesourcery.com \
--to=froydnj@codesourcery.com \
--cc=av1474@comtv.ru \
--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 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.