public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@arm.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Shaokun Zhang via Binutils <binutils@sourceware.org>,
	 Shaokun Zhang <zhangshaokun@hisilicon.com>,
	 Jingtao Cai <caijingtao@huawei.com>,
	 Bo Dong <dongbo4@huawei.com>,
	 Richard Earnshaw <rearnsha@arm.com>,
	 Marcus Shawcroft <marcus.shawcroft@arm.com>
Subject: Re: [PATCH RESEND v2] Aarch64: Allow explicit size specifier for predicate operand of {sq, uq, }{incp, decp}
Date: Mon, 12 Sep 2022 10:38:34 +0100	[thread overview]
Message-ID: <mpt8rmp7x0l.fsf@arm.com> (raw)
In-Reply-To: <94c21b51-5872-1e16-8d15-027c21c59112@suse.com> (Jan Beulich's message of "Mon, 12 Sep 2022 10:27:47 +0200")

Jan Beulich <jbeulich@suse.com> writes:
> On 12.09.2022 10:17, Richard Sandiford via Binutils wrote:
>> It's extremely unlikely that the old syntax would be repurposed to mean
>> something else.  Therefore, Richard and I thought that it might be better
>> to continue to accept the old syntax alongside the new syntax in the GNU
>> tools, as a GNU extension to the official assembler spec, without the
>> deprecation message.  Sorry to raise this after so long, and after you'd
>> already done the work.
>
> Isn't it the case already that the old syntax will continue to be accepted,
> by there being new insn entries added without removing the original ones?

Yes, for now.  But the point of deprecation is that it anticipates
removing the old syntax in future.  The suggestion here was instead
to keep the old syntax alongside the new one, without any intention
of removing it.

> IOW is it perhaps that you're asking for the old syntax to remain accepted
> _silently_ (and don't claim this behavior will be removed)? If so, I'd like
> to suggest to perhaps allow for diagnostics, but require a command line
> option to turn them on.

Richard suggested having a “strict” flag that (IIUC) would make gas
stick more rigidly to the ISA definition.  But I think that would be
separate work and would affect quite a few more instructions.  E.g. it
should probably insist on curly brackets around the Z registers in SVE
LD1 and ST1 instructions.  Perhaps it should even insist on # for
immediate operands.

I don't think it's worth having an option specifically for these
instructions in isolation.  And if we did add the strict flag,
I think we should try to make the first implementation relatively
complete, so that its behaviour is somewhat predictable between releases.

Thanks,
Richard

  reply	other threads:[~2022-09-12  9:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  0:53 Shaokun Zhang
2022-02-21 13:13 ` Jan Beulich
2022-03-02  7:36   ` Shaokun Zhang
2022-03-10  9:38     ` Shaokun Zhang
2022-03-10 10:38       ` Jan Beulich
2022-03-10 11:33         ` Shaokun Zhang
2022-03-10 11:50           ` Jan Beulich
2022-03-10 12:24             ` Shaokun Zhang
2022-03-10 12:27 ` Shaokun Zhang
2022-09-12  8:17 ` Richard Sandiford
2022-09-12  8:27   ` Jan Beulich
2022-09-12  9:38     ` Richard Sandiford [this message]
2022-09-28  2:19   ` dongbo (E)
2022-09-30 14:54     ` Richard Sandiford
2022-10-09  1:31       ` dongbo (E)
2022-10-10 10:25         ` Richard Sandiford
2022-10-11  2:19           ` dongbo (E)
2022-10-17  9:33             ` Richard Sandiford
2022-10-18  5:57               ` dongbo (E)

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=mpt8rmp7x0l.fsf@arm.com \
    --to=richard.sandiford@arm.com \
    --cc=binutils@sourceware.org \
    --cc=caijingtao@huawei.com \
    --cc=dongbo4@huawei.com \
    --cc=jbeulich@suse.com \
    --cc=marcus.shawcroft@arm.com \
    --cc=rearnsha@arm.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).