From: Christophe Lyon <christophe.lyon@st.com>
To: Peter Maydell <peter.maydell@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] target-arm: Fix garbage collection of temporaries in Neon emulation.
Date: Tue, 18 Jan 2011 17:58:38 +0100 [thread overview]
Message-ID: <4D35C6BE.5060502@st.com> (raw)
In-Reply-To: <AANLkTikC-TeX9PmbU-GfLY-EKjC0kL4oET=J8XFhwzSh@mail.gmail.com>
On 18.01.2011 16:26, Peter Maydell wrote:
> On 18 January 2011 14:34, Christophe Lyon <christophe.lyon@st.com> wrote:
>> +
>> + /* gen_helper_neon_mull_[su]{8|16} do not free their parameters.
>> + Don't forget to clean them now. */
>> + switch ((size << 1) | u) {
>> + case 0:
>> + case 1:
>> + case 2:
>> + case 3:
>> + dead_tmp(a);
>> + dead_tmp(b);
>> + break;
>> + }
>> }
>
> This seems a rather convoluted way to write "if (size < 2) { ... }"
>
It was for consistency/readability with the preceding paragraph.
>> @@ -5235,9 +5245,12 @@ static int disas_neon_data_insn(CPUState * env,
>> DisasContext *s, uint32_t insn)
>> tmp = neon_load_reg(rn, 0);
>> } else {
>> tmp = tmp3;
>> + /* tmp2 has been discarded in
>> + gen_neon_mull during pass 0, we need to
>> + recreate it. */
>> + tmp2 = neon_get_scalar(size, rm);
>> }
>
> I think this will give the wrong results for instructions where the
> scalar operand is in the same Neon register as the destination
> for the first pass, because calling neon_get_scalar() again will
> do a reload from the Neon register and it might have changed.
> (Also loading it once at the start rather than in every pass is
> more efficient as well as being correct :-))
I agree it's more efficient, but as the temporary is freed by gen_neon_mull, how can I make an efficient copy?
If we decide not to free the temporary in gen_mul[us]_i64_i32, we'll have to make sure clean up is performed correctly in many places.
> Also your patch has hard-coded tabs in it (please see
> CODING_STYLE on the subject of whitespace) and your
> mail client or server has line-wrapped long lines in the patch
> so it doesn't apply cleanly...
Sorry, I know we have some trouble with the mail client or server. Is it possible to send patches as attachments on this list?
next prev parent reply other threads:[~2011-01-18 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 14:34 [Qemu-devel] [PATCH] target-arm: Fix garbage collection of temporaries in Neon emulation Christophe Lyon
2011-01-18 15:26 ` Peter Maydell
2011-01-18 16:58 ` Christophe Lyon [this message]
2011-01-19 14:37 ` Christophe Lyon
2011-01-19 19:12 ` Peter Maydell
2011-01-20 16:52 ` Christophe Lyon
2011-01-26 13:34 ` Aurelien Jarno
2011-01-18 15:36 ` Peter Maydell
2011-01-18 17:00 ` Christophe Lyon
2011-01-18 17:09 ` Peter Maydell
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=4D35C6BE.5060502@st.com \
--to=christophe.lyon@st.com \
--cc=peter.maydell@linaro.org \
--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).