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 patch enabling Arm64's GCS extension
Date: Mon, 12 Feb 2024 08:39:13 +0100 [thread overview]
Message-ID: <671d046a-5592-4099-bf2f-5ccb08d166d6@suse.com> (raw)
Srinath,
may I ask against what specification this was written? There are two
aspects I can't bring in line with what DDI0596 from December has, i.e.
even newer than the patch (dating back to October):
1) gcspopcx, gcspopx, and gcspushx supposedly all have an optional
register operand, which gas 2.42 doesn't accept.
2) gcsstr and gcssttr supposedly have a memory-form 2nd operand, i.e.
a register name enclosed in square brackets. Gas 2.42 expects a
plain register name instead.
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
next reply other threads:[~2024-02-12 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 7:39 Jan Beulich [this message]
2024-02-12 23:42 ` Srinath Parvathaneni
2024-02-29 21:44 ` Srinath Parvathaneni
2024-03-01 6:48 ` 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=671d046a-5592-4099-bf2f-5ccb08d166d6@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).