public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yury Khrustalev <Yury.Khrustalev@arm.com>
To: Richard Earnshaw <Richard.Earnshaw@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/1] aarch64: Sync aarch64-sys-regs.def with Binutils
Date: Wed, 20 Mar 2024 14:00:36 +0000	[thread overview]
Message-ID: <3276DCE2-295F-4449-939B-38C5C31E23F8@arm.com> (raw)
In-Reply-To: <e2e01bc1-c076-4d14-97cb-b04e5a805cb9@arm.com>

Hi Richard,

> On 20 Mar 2024, at 1:55 PM, Richard Earnshaw (lists) <Richard.Earnshaw@arm.com> wrote:
> 
> On 20/03/2024 11:21, Yury Khrustalev wrote:
>> This patch updates `aarch64-sys-regs.def', bringing it into sync with
>> the Binutils source.
>> 
>> gcc/ChangeLog:
>> 
>>     * config/aarch64/aarch64-sys-regs.def: Copy from Binutils.
> 
> Thanks, I've pushed this.  It's trivial enough and there's value of keeping it in sync with binutils.

Thanks!

> 
> One comment though, there should be one hard tab before "* config/..."; you seem to have some other random characters there that looked like white space.

Thanks for the feedback, I'll make sure to avoid this in the future patches.

> 
> R.
> 
>> ---
>> gcc/config/aarch64/aarch64-sys-regs.def | 1 +
>> 1 file changed, 1 insertion(+)
>> 
>> diff --git a/gcc/config/aarch64/aarch64-sys-regs.def b/gcc/config/aarch64/aarch64-sys-regs.def
>> index 6a948171d6e..8b65673a5d6 100644
>> --- a/gcc/config/aarch64/aarch64-sys-regs.def
>> +++ b/gcc/config/aarch64/aarch64-sys-regs.def
>> @@ -521,6 +521,7 @@
>>   SYSREG ("id_aa64isar0_el1", CPENC (3,0,0,6,0), F_REG_READ, AARCH64_NO_FEATURES)
>>   SYSREG ("id_aa64isar1_el1", CPENC (3,0,0,6,1), F_REG_READ, AARCH64_NO_FEATURES)
>>   SYSREG ("id_aa64isar2_el1", CPENC (3,0,0,6,2), F_REG_READ, AARCH64_NO_FEATURES)
>> +  SYSREG ("id_aa64isar3_el1", CPENC (3,0,0,6,3), F_REG_READ, AARCH64_NO_FEATURES)
>>   SYSREG ("id_aa64mmfr0_el1", CPENC (3,0,0,7,0), F_REG_READ, AARCH64_NO_FEATURES)
>>   SYSREG ("id_aa64mmfr1_el1", CPENC (3,0,0,7,1), F_REG_READ, AARCH64_NO_FEATURES)
>>   SYSREG ("id_aa64mmfr2_el1", CPENC (3,0,0,7,2), F_REG_READ, AARCH64_NO_FEATURES)
> 

Kind regards,
Yury



      reply	other threads:[~2024-03-20 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-20 11:21 [PATCH 0/1] " Yury Khrustalev
2024-03-20 11:21 ` [PATCH 1/1] " Yury Khrustalev
2024-03-20 13:55   ` Richard Earnshaw (lists)
2024-03-20 14:00     ` Yury Khrustalev [this message]

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=3276DCE2-295F-4449-939B-38C5C31E23F8@arm.com \
    --to=yury.khrustalev@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).