From: Nick Clifton <nickc@redhat.com>
To: Tamar Christina <Tamar.Christina@arm.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Cc: nd <nd@arm.com>, Richard Earnshaw <Richard.Earnshaw@arm.com>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: [PATCH][Binutils][AArch64] Fix cfinv disassembly issues
Date: Fri, 24 Jan 2020 11:44:00 -0000 [thread overview]
Message-ID: <f8ae24df-17b0-8b70-e338-5d5120402c7a@redhat.com> (raw)
In-Reply-To: <20200122134418.GA32460@arm.com>
Hi Tamar,
> Ok for master? and for backport to binutils-2.33 branch and to 2.34 once branch is open?
Approved for all three. Since this is a bug fix, it is OK to apply to the 2.34 branch now.
> gas/ChangeLog:
> 2020-01-22 Tamar Christina <tamar.christina@arm.com>
>
> PR 25403
> * testsuite/gas/aarch64/armv8_4-a.d: Add cfinv.
> * testsuite/gas/aarch64/armv8_4-a.s: Likewise.
>
> opcodes/ChangeLog:
> 2020-01-22 Tamar Christina <tamar.christina@arm.com>
>
> PR 25403
> * aarch64-tbl.h (struct aarch64_opcode): Re-order cfinv.
Cheers
Nick
prev parent reply other threads:[~2020-01-24 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 13:44 Tamar Christina
2020-01-24 11:44 ` 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=f8ae24df-17b0-8b70-e338-5d5120402c7a@redhat.com \
--to=nickc@redhat.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Tamar.Christina@arm.com \
--cc=binutils@sourceware.org \
--cc=nd@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).