public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: srinath <srinath.parvathaneni@arm.com>
Cc: richard.earnshaw@arm.com, nickc@redhat.com, binutils@sourceware.org
Subject: Re: [PATCH v2 4/7][Binutils] aarch64: Fix sve2p1 ld[1-4]/st[1-4]q instruction operands.
Date: Wed, 22 May 2024 12:23:55 +0200	[thread overview]
Message-ID: <86ddbde6-54bf-4cee-aad8-58a3dacc6fd2@suse.com> (raw)
In-Reply-To: <20240522100439.1050296-7-srinath.parvathaneni@arm.com>

On 22.05.2024 12:04, srinath wrote:
> This patch fixes encoding and syntax for sve2p1 instructions as mentioned below,
> for the issues reported here.
> https://sourceware.org/pipermail/binutils/2024-February/132408.html
> 
> 1) ld1q and st1q first register operand to accept enclosed figure braces.
> 2) ld2q, ld3q, ld4q, st2q, st3q, and st4q instructions to accept wrapping
>    sequence of vector registers.
> 3) Fixes the encoding for bits 13 and 14 for ld2q's scalar plus scalar encoding.
> 4) ld3q/st3q and ld4q/st4q scalar plus immediate forms accepts multiple of 3 and 4
> respectively.

3) and 4) were meanwhile fixed already, weren't they?

Jan

  reply	other threads:[~2024-05-22 10:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 10:04 [PATCH 0/7][Binutils] aarch64: Fix the FEAT_SVE2p1 related issues srinath
2024-05-22 10:04 ` [PATCH 1/7][Binutils] aarch64: Enable mandatory feature bits for v9.4-A srinath
2024-05-22 10:04 ` [PATCH v2 2/7][Binutils] aarch64: Fix sve2p1 dupq instruction operands srinath
2024-05-22 10:04 ` [PATCH v1 2-R/7][Binutils] aarch64: Fix sve2p1 dupq instruction operands (regenerated files) srinath
2024-05-22 10:04 ` [PATCH 3/7][Binutils] aarch64: Fix sve2p1 extq instruction operands srinath
2024-05-22 10:04 ` [PATCH 3-R/7][Binutils] aarch64: Fix sve2p1 extq instruction operands (regenerated files) srinath
2024-05-22 10:04 ` [PATCH v2 4/7][Binutils] aarch64: Fix sve2p1 ld[1-4]/st[1-4]q instruction operands srinath
2024-05-22 10:23   ` Jan Beulich [this message]
2024-05-22 11:56     ` Srinath Parvathaneni
2024-05-22 10:04 ` [PATCH v1 4-R/7][Binutils] aarch64: Fix sve2p1 ld[1-4]/st[1-4]q instruction operands (regenerated files) srinath
2024-05-22 10:04 ` [PATCH v1 5/7][BINUTILS] aarch64: Fix the wrong constraint used for sve2p1 instructions srinath
2024-05-22 10:04 ` [PATCH v1 6/7][Binutils] aarch64: Add extra tests for sve2p1 min max instructions srinath
2024-05-22 10:04 ` [PATCH v1 7/7][Binutils] aarch64: Fix FEAT_B16B16 sve2 instruction constraints srinath
2024-05-22 10:04 ` [PATCH v1 7-R/7][Binutils] aarch64: Fix FEAT_B16B16 sve2 instruction constraints (regenerated files) srinath
2024-06-07 12:52 ` [PATCH 0/7][Binutils] aarch64: Fix the FEAT_SVE2p1 related issues Srinath Parvathaneni
2024-06-07 13:23   ` Richard Earnshaw (lists)
2024-06-07 13:30     ` Srinath Parvathaneni
2024-06-07 14:27       ` Richard Earnshaw (lists)

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=86ddbde6-54bf-4cee-aad8-58a3dacc6fd2@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=richard.earnshaw@arm.com \
    --cc=srinath.parvathaneni@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).