From: Aurelien Jarno <aurelien@aurel32.net>
To: Richard Henderson <rth@twiddle.net>
Cc: alex.bennee@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Replace trunc_shr_i32 with extr[lh]
Date: Fri, 31 Jul 2015 17:21:02 +0200 [thread overview]
Message-ID: <20150731152102.GA29132@aurel32.net> (raw)
In-Reply-To: <1438352671-6466-1-git-send-email-rth@twiddle.net>
On 2015-07-31 07:24, Richard Henderson wrote:
> I'd prefer to use these two patches instead of Aurelien's
> patch to rename INDEX_OP_trunc_i32. Thoughts?
That sounds better to me than the current trunc_shr_i32 implementation.
I'll send a new version of my patchset based on this one.
Reviewed-by: Aurelien Jarno <aurelien@aurel32.net>
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2015-07-31 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 14:24 [Qemu-devel] [PATCH 0/2] Replace trunc_shr_i32 with extr[lh] Richard Henderson
2015-07-31 14:24 ` [Qemu-devel] [PATCH 1/2] tcg: Split trunc_shr_i32 opcode into extr[lh]_i64_i32 Richard Henderson
2015-07-31 15:21 ` 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=20150731152102.GA29132@aurel32.net \
--to=aurelien@aurel32.net \
--cc=alex.bennee@linaro.org \
--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 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).