From: Richard Henderson <richard.henderson@linaro.org>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Beata Michalska <beata.michalska@linaro.org>
Subject: Re: [Qemu-devel] [PATCH] tcg/aarch64: Fix output of extract2 opcodes
Date: Thu, 11 Jul 2019 13:45:18 +0200 [thread overview]
Message-ID: <d92c85b6-f7a4-71b8-9601-03d8975b5212@linaro.org> (raw)
In-Reply-To: <CAL1e-=j8J0WLUjhaOvecSU3VtRf5W+zP-Ydi_kZth4BYV_cXtg@mail.gmail.com>
On 7/10/19 8:12 PM, Aleksandar Markovic wrote:
> On Tue, Jul 9, 2019 at 8:56 PM Richard Henderson
> <richard.henderson@linaro.org> wrote:
>>
>> The aarch64 argument ordering for the operands is big-endian,
>> whereas the tcg argument ordering is little-endian. Use REG0
>> so that we honor the rZ constraints.
>
> Hello, Richard.
>
> If endian and rZ constraints are unrelated problems, then I think the
> commit message
> should be:
>
> "This patch fixes two problem:
>
> - endianness: the aarch64 argument ordering for the operands is
> big-endian, whereas the tcg argument ordering is little-endian.
>
> - rZ constrains: REG0() macro should be applied to the affected
> arguments."
That's fair.
> One could argue that in this case the patch this should be actually two patches.
> This is better because of bisectability. The number of line in the
> patch doesn't matter.
Well, nothing between the faulty commit (Fixes: 464c2969d5d) and the second of
the two prospective patches is really bisectable. For the given test case, all
points in between will fail at runtime, even if each point compiles.
Therefore I don't see the point in separating the two changes.
> Would you be so kind to consider my opinion?
Yes. Thanks for the expanded opinion.
I plan to change the commit message to:
---
tcg/aarch64: Fix output of extract2 opcodes
This patch fixes two problems:
(1) The inputs to the EXTR insn were reversed,
(2) The input constraints use rZ, which means that we need to use
the REG0 macro in order to supply XZR for a constant 0 input.
r-b, s-o-b, etc
---
Does that seem sufficient to you?
r~
next prev parent reply other threads:[~2019-07-11 11:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 18:48 [Qemu-devel] [PATCH] tcg/aarch64: Fix output of extract2 opcodes Richard Henderson
2019-07-10 9:22 ` Aleksandar Markovic
2019-07-10 9:48 ` Richard Henderson
2019-07-10 10:04 ` Aleksandar Markovic
2019-07-10 15:40 ` Peter Maydell
2019-07-10 17:28 ` Aleksandar Markovic
2019-07-10 10:22 ` Philippe Mathieu-Daudé
2019-07-10 10:42 ` Alex Bennée
2019-07-10 18:12 ` Aleksandar Markovic
2019-07-11 11:45 ` Richard Henderson [this message]
2019-07-11 17:06 ` Aleksandar Markovic
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=d92c85b6-f7a4-71b8-9601-03d8975b5212@linaro.org \
--to=richard.henderson@linaro.org \
--cc=aleksandar.m.mail@gmail.com \
--cc=beata.michalska@linaro.org \
--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).