public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Srinath Parvathaneni <srinath.parvathaneni@arm.com>
Cc: Binutils <binutils@sourceware.org>,
	Richard Earnshaw <rearnsha@arm.com>,
	Marcus Shawcroft <marcus.shawcroft@arm.com>,
	Nick Clifton <nickc@redhat.com>
Subject: your patches enabling Arm64's SVE 2.1 extension
Date: Mon, 12 Feb 2024 09:00:16 +0100	[thread overview]
Message-ID: <bd28bee0-6361-42d6-964f-96a96c1811c2@suse.com> (raw)

Srinath,

may I ask against what specification these were written? There are many
aspects I can't bring in line with what DDI0596 from December has, i.e.
even newer than the patch (dating back to October), to a degree that I
have to even question gas/NEWS stating (supposedly complete) support for
the feature:

1) dupq uses encodings different from the doc, in part resulting in
   supposedly reserved encodings (tsz=0).

2) extq uses syntax (operands) pretty different from what the doc says.

3) ld1q and st1q expect a plain first register operand, not one enclosed
   in figure braces.

4) ld2q, ld3q, ld4q, st2q, st3q, and st4q don't permit a wrapping
   sequence of vector registers, when the doc using "modulo" imo can't be
   read any way other than meaning to permit that.

5) ld2q's scalar plus scalar encoding has bits 13 and 14 set, which is
   inconsistent not only with the doc, but also with ld3q and ld4q.

6) ld3q/st3q and ld4q/st4q scalar plus immediate forms demand an immediate
   that's a multiple of 2, when the doc says 3 and 4 respectively.

7) orqv, pmov, tblq, tbxq, uzpq{1,2}, and zipq{1,2} are entirely missing.

Despite being newer it's of course possible that documentation is what
actually needs fixing. Can you please clarify which way it is?

Thanks, Jan

             reply	other threads:[~2024-02-12  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  8:00 Jan Beulich [this message]
2024-02-12 23:16 ` Srinath Parvathaneni
2024-02-13  7:24   ` Jan Beulich
2024-02-13  9:55     ` Nick Clifton
2024-02-13 10:48       ` Jan Beulich
2024-02-13 11:11         ` Nick Clifton
2024-02-13 11:39           ` Jan Beulich
2024-03-11  7:14           ` Jan Beulich
2024-02-15 11:21     ` Andrew Carlotti

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=bd28bee0-6361-42d6-964f-96a96c1811c2@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=marcus.shawcroft@arm.com \
    --cc=nickc@redhat.com \
    --cc=rearnsha@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).