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 0/8] aarch64: Enable the RCpc3 (Release Consistency) extension
Date: Mon, 15 Jan 2024 11:55:50 +0000 [thread overview]
Message-ID: <c7509e14-b08a-429a-ba76-81f5621d3543@redhat.com> (raw)
In-Reply-To: <20240112165637.2522719-1-victor.donascimento@arm.com>
On 1/12/24 16:56, Victor Do Nascimento wrote:
> Given the introduction of the third set of Release Consistency
> processor consistent (RCpc) memory model-compliant instructions in
> the form of FEAT_LRCPC3 as an optional extension from Armv8.2-a
> onward, this patch series adds the relevant machinery to Binutils to
> add support for the instructions it adds to the instruction set.
>
> Victor Do Nascimento (8):
> aarch64: rcpc3: Add +rcpc3 architectural feature support flag
> aarch64: rcpc3: Create implicit load/store size calc function
> aarch64: rcpc3: Define address operand fields and inserter/extractors
> aarch64: rcpc3: New RCPC3_ADDR operand types
> aarch64: rcpc3: add support in general_constraint_met_p
> aarch64: rcpc3: Define RCPC3_INSN macro
> aarch64: rcpc3: Add integer load/store insns
> aarch64: rcpc3: Add FP load/store insns
Patch series approved - please apply. (You will need to rebase your
patches as they do not apply cleanly to the latest mainline sources).
If you are quick you can get this series in before the 2.42 branch
is created. If not, you have approval to apply the patch series to
the branch as well.
Cheers
Nick
next prev parent reply other threads:[~2024-01-15 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 16:56 Victor Do Nascimento
2024-01-12 16:56 ` [PATCH 1/8] aarch64: rcpc3: Add +rcpc3 architectural feature support flag Victor Do Nascimento
2024-01-12 16:56 ` [PATCH 2/8] aarch64: rcpc3: Create implicit load/store size calc function Victor Do Nascimento
2024-01-12 16:56 ` [PATCH 3/8] aarch64: rcpc3: Define address operand fields and inserter/extractors Victor Do Nascimento
2024-01-12 16:56 ` [PATCH 4/8] aarch64: rcpc3: New RCPC3_ADDR operand types Victor Do Nascimento
2024-01-12 16:56 ` [PATCH 5/8] aarch64: rcpc3: add support in general_constraint_met_p Victor Do Nascimento
2024-01-12 16:56 ` [PATCH 6/8] aarch64: rcpc3: Define RCPC3_INSN macro Victor Do Nascimento
2024-01-12 16:56 ` [PATCH 7/8] aarch64: rcpc3: Add integer load/store insns Victor Do Nascimento
2024-01-12 16:56 ` [PATCH 8/8] aarch64: rcpc3: Add FP " Victor Do Nascimento
2024-01-15 11:55 ` Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-12 16:54 [PATCH 0/8] aarch64: Enable the RCpc3 (Release Consistency) extension Victor Do Nascimento
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=c7509e14-b08a-429a-ba76-81f5621d3543@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).