From: Richard Henderson <richard.henderson@linaro.org>
To: Kirill Batuzov <batuzovk@ispras.ru>, qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH RFC 3/3] tcg/optimize: handle vector loads and stores during copy propagation
Date: Wed, 22 Nov 2017 09:19:58 +0100 [thread overview]
Message-ID: <842a000d-11bf-a3f4-e1ac-8f0f6ed07324@linaro.org> (raw)
In-Reply-To: <c4be5f68-2093-db46-c917-953578a22d46@linaro.org>
On 11/22/2017 09:06 AM, Richard Henderson wrote:
> On 11/09/2017 03:41 PM, Kirill Batuzov wrote:
>> + } else if (re == INDEX_op_mov_vec) {
>> + if (ts_are_copies(arg_temp(op->args[0]), ml->copy)) {
>> + tcg_op_remove(s, op);
>> + break;
>> + }
>> + op->opc = re;
>> + op->args[1] = temp_arg(find_better_copy(s, ml->copy));
>> + op->args[2] = op->args[3];
>> } else {
>
> Why don't you send this through tcg_opt_gen_mov as with mov_i32 and mov_i64?
Oh nevermind, you're handling the extra size operand that was in v3. Well,
good news is that you don't need that anymore. ;-)
r~
prev parent reply other threads:[~2017-11-22 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 14:41 [Qemu-devel] [PATCH RFC 0/3] TCG: do copy propagation through memory locations Kirill Batuzov
2017-11-09 14:41 ` [Qemu-devel] [PATCH RFC 1/3] tcg: support MOV_VEC and MOVI_VEC opcodes in register allocator Kirill Batuzov
2017-11-22 8:01 ` Richard Henderson
2017-11-09 14:41 ` [Qemu-devel] [PATCH RFC 2/3] tcg/optimize: do copy propagation for memory locations Kirill Batuzov
2017-11-22 8:44 ` Richard Henderson
2017-11-23 11:16 ` Kirill Batuzov
2017-11-09 14:41 ` [Qemu-devel] [PATCH RFC 3/3] tcg/optimize: handle vector loads and stores during copy propagation Kirill Batuzov
2017-11-22 8:06 ` Richard Henderson
2017-11-22 8:19 ` Richard Henderson [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=842a000d-11bf-a3f4-e1ac-8f0f6ed07324@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=batuzovk@ispras.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 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).