From: Vineet Gupta <vineetg@rivosinc.com>
To: Christoph Muellner <cmuellner@gcc.gnu.org>, gcc-patches@gcc.gnu.org
Cc: Kito Cheng <kito.cheng@sifive.com>,
gnu-toolchain <gnu-toolchain@rivosinc.com>
Subject: Re: [PATCH v2 00/10] [RISC-V] Atomics improvements [PR100265/PR100266]
Date: Tue, 11 Oct 2022 12:06:27 -0700 [thread overview]
Message-ID: <f2ba9aa4-5c21-c352-06c2-385d30526f8b@rivosinc.com> (raw)
In-Reply-To: <20210505193651.2075405-1-cmuellner@gcc.gnu.org>
Hi Christoph, Kito,
On 5/5/21 12:36, Christoph Muellner via Gcc-patches wrote:
> This series provides a cleanup of the current atomics implementation
> of RISC-V:
>
> * PR100265: Use proper fences for atomic load/store
> * PR100266: Provide programmatic implementation of CAS
>
> As both are very related, I merged the patches into one series.
>
> The first patch could be squashed into the following patches,
> but I found it easier to understand the chances with it in place.
>
> The series has been tested as follows:
> * Building and testing a multilib RV32/64 toolchain
> (bootstrapped with riscv-gnu-toolchain repo)
> * Manual review of generated sequences for GCC's atomic builtins API
>
> The programmatic re-implementation of CAS benefits from a REE improvement
> (see PR100264):
> https://gcc.gnu.org/pipermail/gcc-patches/2021-April/568680.html
> If this patch is not in place, then an additional extension instruction
> is emitted after the SC.W (in case of RV64 and CAS for uint32_t).
>
> Further, the new CAS code requires cbranch INSN helpers to be present:
> https://gcc.gnu.org/pipermail/gcc-patches/2021-May/569689.html
I was wondering is this patchset is blocked on some technical grounds.
Thx,
-Vineet
> Changes for v2:
> * Guard LL/SC sequence by compiler barriers ("blockage")
> (suggested by Andrew Waterman)
> * Changed commit message for AMOSWAP->STORE change
> (suggested by Andrew Waterman)
> * Extracted cbranch4 patch from patchset (suggested by Kito Cheng)
> * Introduce predicate riscv_sync_memory_operand (suggested by Jim Wilson)
> * Fix small code style issue
>
> Christoph Muellner (10):
> RISC-V: Simplify memory model code [PR 100265]
> RISC-V: Emit proper memory ordering suffixes for AMOs [PR 100265]
> RISC-V: Eliminate %F specifier from riscv_print_operand() [PR 100265]
> RISC-V: Use STORE instead of AMOSWAP for atomic stores [PR 100265]
> RISC-V: Emit fences according to chosen memory model [PR 100265]
> RISC-V: Implement atomic_{load,store} [PR 100265]
> RISC-V: Model INSNs for LR and SC [PR 100266]
> RISC-V: Add s.ext-consuming INSNs for LR and SC [PR 100266]
> RISC-V: Provide programmatic implementation of CAS [PR 100266]
> RISC-V: Introduce predicate "riscv_sync_memory_operand" [PR 100266]
>
> gcc/config/riscv/riscv-protos.h | 1 +
> gcc/config/riscv/riscv.c | 136 +++++++++++++-------
> gcc/config/riscv/sync.md | 216 +++++++++++++++++++++-----------
> 3 files changed, 235 insertions(+), 118 deletions(-)
>
next prev parent reply other threads:[~2022-10-11 19:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 19:36 Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 01/10] RISC-V: Simplify memory model code [PR 100265] Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 02/10] RISC-V: Emit proper memory ordering suffixes for AMOs " Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 03/10] RISC-V: Eliminate %F specifier from riscv_print_operand() " Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 04/10] RISC-V: Use STORE instead of AMOSWAP for atomic stores " Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 05/10] RISC-V: Emit fences according to chosen memory model " Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 06/10] RISC-V: Implement atomic_{load,store} " Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 07/10] RISC-V: Model INSNs for LR and SC [PR 100266] Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 08/10] RISC-V: Add s.ext-consuming " Christoph Muellner
2021-05-05 19:36 ` [PATCH v2 09/10] RISC-V: Provide programmatic implementation of CAS " Christoph Muellner
2021-05-06 0:27 ` Jim Wilson
2021-05-05 19:36 ` [PATCH v2 10/10] RISC-V: Introduce predicate "riscv_sync_memory_operand" " Christoph Muellner
2022-10-11 19:06 ` Vineet Gupta [this message]
2022-10-11 19:31 ` [PATCH v2 00/10] [RISC-V] Atomics improvements [PR100265/PR100266] Palmer Dabbelt
2022-10-11 20:46 ` Christoph Müllner
2022-10-11 23:31 ` Vineet Gupta
2022-10-12 0:15 ` Palmer Dabbelt
2022-10-12 8:03 ` Christoph Müllner
2022-10-13 23:11 ` Jeff Law
2022-10-12 17:16 ` Andrea Parri
2022-10-20 19:01 ` Andrea Parri
2022-10-29 5:02 ` Jeff Law
2022-10-13 23:04 ` Jeff Law
2022-10-13 22:39 ` Jeff Law
2022-10-13 23:14 ` Palmer Dabbelt
2022-10-14 11:03 ` Christoph Müllner
2022-10-14 20:39 ` Jeff Law
2022-10-14 21:57 ` Palmer Dabbelt
2022-10-15 0:31 ` Palmer Dabbelt
2022-10-14 0:14 ` Vineet Gupta
2022-10-11 23:14 ` Jeff Law
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=f2ba9aa4-5c21-c352-06c2-385d30526f8b@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=cmuellner@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=kito.cheng@sifive.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).