From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Claudio Bantaloukas <claudio.bantaloukas@arm.com>,
binutils@sourceware.org
Cc: nd@arm.com
Subject: Re: [PATCH] arm: Fix MVE vmla encoding
Date: Fri, 17 May 2024 15:31:12 +0100 [thread overview]
Message-ID: <e99ae61b-84f4-4379-8014-55e5785e51c7@arm.com> (raw)
In-Reply-To: <20240415100020.497574-1-claudio.bantaloukas@arm.com>
On 15/04/2024 11:00, Claudio Bantaloukas wrote:
>
> Bit 12 of the first halfword in the VMLA instruction is listed as (0)
> in the ARMARM (document DDI0553B.w, version ID07072023).
> This means that the instruction does not discriminate between signed
> and unsigned types and processing elements do not use the bit.
> The encoding used by gas was based on an older version
> of the document that made the sign important.
> This change makes it possible to use vmla.i8 (16,32) in addition to
> vmla.u8 and vmla.s8 mnemonics, with the i8, i16 and i32 aliases becoming
> the default when disassembling.
> The generated encoding sets bit 12 to 0, compatibly with other
> assembler implementations.
> ---
> Hi,
>
> Is this Ok for master? I do not have commit rights, if OK, can someone commit on my behalf please?
> Tested on arm-none-eabi.
>
> Thanks,
> Claudio Bantaloukas
>
> gas/config/tc-arm.c | 4 +-
> gas/testsuite/gas/arm/mve-vmla.d | 3383 ++++++++++++++++++------------
> gas/testsuite/gas/arm/mve-vmla.s | 8 +-
> opcodes/arm-dis.c | 2 +-
> 4 files changed, 2041 insertions(+), 1356 deletions(-)
>
I think this patch is incomplete. The current armv8-m Arm ARM also shows that VMLAS was also changed in a similar manner. Were any other instructions affected?
R.
prev parent reply other threads:[~2024-05-17 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 10:00 Claudio Bantaloukas
2024-04-23 17:04 ` Nick Clifton
2024-04-23 17:36 ` Claudio Bantaloukas
2024-04-24 10:47 ` Nick Clifton
2024-05-17 14:52 ` Richard Earnshaw (lists)
2024-05-17 14:31 ` Richard Earnshaw (lists) [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=e99ae61b-84f4-4379-8014-55e5785e51c7@arm.com \
--to=richard.earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=claudio.bantaloukas@arm.com \
--cc=nd@arm.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).