From: Jan Beulich <jbeulich@suse.com>
To: Shaokun Zhang <zhangshaokun@hisilicon.com>
Cc: Jingtao Cai <caijingtao@huawei.com>, Bo Dong <dongbo4@huawei.com>,
binutils@sourceware.org
Subject: Re: [PATCH] Fix the disassembly of the AArch64 SVE DECP/INCP/SQDECP/SQINCP instruction.
Date: Mon, 7 Feb 2022 10:44:38 +0100 [thread overview]
Message-ID: <8b5990b6-a9c0-8365-17b0-fcb99b22a3f0@suse.com> (raw)
In-Reply-To: <20220207093441.55725-1-zhangshaokun@hisilicon.com>
On 07.02.2022 10:34, Shaokun Zhang via Binutils wrote:
> From: Jingtao Cai <caijingtao@huawei.com>
>
> This patch fix qualifier for the AArch64 SVE DECP/INCP/SQDECP/SQINCP instruction, which take the predicate size specifier:
> DECP <Zdn>.<T>, <Pm>.<T>
> INCP <Zdn>.<T>, <Pm>.<T>
> SQINCP <Zdn>.<T>, <Pm>.<T>
> SQDECP <Zdn>.<T>, <Pm>.<T>
>
> Omitted predicate size specifier will be prohibited in a future release of the architecture, please refer to Arm A64 Instruction set documentation for Armv8-A
> architecture profile, see document[0].
>
> [0]: https://developer.arm.com/documentation/ddi0596/2021-12/SVE-Instructions/DECP--vector---Decrement-vector-by-count-of-true-predicate-elements-
>
> E.g. :
>
> DECP Z1.H, P0.H
>
> This patch adds support for this kind of operand.
>
> DECP Z1.H, P0
>
> This instruction leads to messages:
> Assembler messages:
> Error: operand mismatch -- `decp Z1.h,P0'
IOW unlike the title suggests you change not only the disassembly
logic. Wouldn't it be better to make this a warning initially, and
convert to an error only a few releases later? That way people
don't need to immediately fix their code.
> did you mean this?
> decp z1.h, p0.h
> other valid variant(s):
> decp z1.s, p0
> decp z1.d, p0
Isn't this misleading? Should these "other valid variant(s)" also
be output with suffixes?
Jan
next prev parent reply other threads:[~2022-02-07 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 9:34 Shaokun Zhang
2022-02-07 9:44 ` Jan Beulich [this message]
2022-02-09 0:56 ` Shaokun Zhang
2022-02-09 7:20 ` Jan Beulich
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=8b5990b6-a9c0-8365-17b0-fcb99b22a3f0@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=caijingtao@huawei.com \
--cc=dongbo4@huawei.com \
--cc=zhangshaokun@hisilicon.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).