From: Nick Clifton <nickc@redhat.com>
To: Victor Do Nascimento <victor.donascimento@arm.com>,
binutils@sourceware.org
Cc: richard.earnshaw@arm.com
Subject: Re: [PATCH] aarch64: Fix error in THE system register checking
Date: Thu, 9 Nov 2023 14:08:12 +0000 [thread overview]
Message-ID: <36447828-01ee-4f8d-93c5-5a239f1380d4@redhat.com> (raw)
In-Reply-To: <20231109134413.3536899-1-victor.donascimento@arm.com>
Hi Victor,
> The erroneous omission of a "reg_value == " in the THE system register
> encoding check added in [1] led to an error which was not picked up in
> GCC but which was flagged in Clang due to its use of
> [-Werror,-Wconstant-logical-operand] check. Together with this fix we
> add a new test for the THE registers to pick up their illegal use,
> adding an extra and important layer of validation.
>
> Furthermore, in separating system register from instruction
> implementation (with which only the former was of concern in the cited
> patch), additions made to `aarch64-tbl.h' are rolled back so
> that these can be added later when adding THE instructions to the
> codebase, a more natural place for these changes.
>
> [1] https://sourceware.org/pipermail/binutils/2023-November/130314.html
>
> opcodes/ChangeLog:
>
> * aarch64-opc.c (aarch64_sys_ins_reg_supported_p): Fix typo.
> * aarch64-tbl.h (THE): Remove.
> (aarch64_feature_set aarch64_feature_the): Likewise.
>
> gas/ChangeLog:
>
> * testsuite/gas/aarch64/illegal-sysreg-8.l: Add tests for THE
> system registers.
> * testsuite/gas/aarch64/illegal-sysreg-8.s: Likewise.
Approved - please apply.
Cheers
Nick
prev parent reply other threads:[~2023-11-09 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 13:43 Victor Do Nascimento
2023-11-09 14:08 ` Nick Clifton [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=36447828-01ee-4f8d-93c5-5a239f1380d4@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=richard.earnshaw@arm.com \
--cc=victor.donascimento@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).