From: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
Nick Clifton <nickc@redhat.com>
Subject: Re: [PATCH] aarch64: Add support for Common Short Sequence Compression extension
Date: Fri, 11 Nov 2022 09:02:59 +0000 [thread overview]
Message-ID: <5e285461-ece0-3bee-8835-d6c14f5c00c0@arm.com> (raw)
In-Reply-To: <f523e13e-a9c9-c572-512d-3c24451cf9eb@arm.com>
Ping
On 07/11/2022 09:47, Andre Vieira (lists) via Binutils wrote:
> Fixed the whitespace typo.
>
> On 31/10/2022 16:33, Andre Vieira (lists) via Binutils wrote:
>>
>> On 31/10/2022 13:40, Jan Beulich wrote:
>>> On 31.10.2022 12:45, Andre Vieira (lists) wrote:
>>>> They are in the Arm A-profile A64 Instruction Set document on
>>>> developer.arm.com. I don't know if this link is a permanent one,
>>>> but for
>>>> now
>>>> https://documentation-service.arm.com/static/633d9270da191e7fe057eb97
>>>> should work.
>>>> If you look for FEAT_CSSC in that document you will find the relevant
>>>> instructions and their encoding.
>>> Thanks. One minor remark on the patch itself as I was looking over it:
>>> All new aarch64_opcode_table[] entries look to have their 2nd commas
>>> slightly misplaced.
>>>
>>> Jan
>> Yeah you are right, I'll fix that before committing, if it gets
>> accepted without any other comments that is.
>>
>> Thanks,
>> Andre
next prev parent reply other threads:[~2022-11-11 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:14 Andre Vieira (lists)
2022-10-31 11:29 ` Jan Beulich
2022-10-31 11:45 ` Andre Vieira (lists)
2022-10-31 13:40 ` Jan Beulich
2022-10-31 16:33 ` Andre Vieira (lists)
2022-11-07 9:47 ` Andre Vieira (lists)
2022-11-11 9:02 ` Andre Vieira (lists) [this message]
2022-11-14 13:44 ` Nick Clifton
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=5e285461-ece0-3bee-8835-d6c14f5c00c0@arm.com \
--to=andre.simoesdiasvieira@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).