From: Jeff Law <jeffreyalaw@gmail.com>
To: David Abdurachmanov <david.abd@gmail.com>,
Kito Cheng <kito.cheng@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Patrick O'Neill <patrick@rivosinc.com>
Subject: Re: [PATCH v4] RISC-V: Add support for inlining subword atomic operations
Date: Tue, 15 Nov 2022 20:53:06 -0700 [thread overview]
Message-ID: <11934bab-4a83-dd3b-7421-a1bf0d3e1439@gmail.com> (raw)
In-Reply-To: <CAJCwxyC=RtHOm4t3p6tzBbJCqNttyK_uEBXjCPJ01_RzAE30Uw@mail.gmail.com>
On 10/28/22 10:55, David Abdurachmanov via Gcc-patches wrote:
> On Fri, Sep 2, 2022 at 1:09 PM Kito Cheng via Gcc-patches <
> gcc-patches@gcc.gnu.org> wrote:
>
>> LGTM with minor comments, it's time to move forward, thanks Patrick and
>> Palmer.
>>
> Ping.
>
> Any plans to finally land this one for GCC 13?
>
> The hope is that this patch would make life significantly easier for
> distributions. There are way too many packages failing to build due to
> sub-word atomics, which is highly annoying considering that it's not
> consistent between package versions. Build times on riscv64 are extremely
> long which makes it even more annoying. Would love to see this finally
> fixed.
It could well be the case that this gets punted. Atomics are a bit of a
mess at the moment and we're still trying to figure out the best way
forward. It's not forgotten though.
jeff
next prev parent reply other threads:[~2022-11-16 3:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 21:58 Palmer Dabbelt
2022-09-02 10:08 ` Kito Cheng
2022-10-28 16:55 ` David Abdurachmanov
2022-11-16 3:53 ` Jeff Law [this message]
2023-04-18 14:28 ` [PATCH v5] RISCV: Inline subword atomic ops Patrick O'Neill
2023-04-18 15:06 ` Andreas Schwab
2023-04-18 16:39 ` [PATCH v6] " Patrick O'Neill
2023-04-18 20:17 ` Palmer Dabbelt
2023-04-18 21:41 ` [PATCH v7] " Patrick O'Neill
2023-04-24 17:20 ` Patrick O'Neill
2023-04-25 5:52 ` Jeff Law
2023-04-25 15:20 ` Patrick O'Neill
2023-04-26 2:27 ` Jeff Law
2023-04-26 17:01 ` [committed] " Patrick O'Neill
2023-05-02 20:34 ` Patrick O'Neill
2023-05-03 6:32 ` Jeff Law
2023-05-03 9:49 ` Richard Biener
2023-05-03 14:14 ` Palmer Dabbelt
2023-05-03 15:13 ` Jeff Law
2023-05-03 15:33 ` Palmer Dabbelt
2023-05-03 16:13 ` Patrick O'Neill
2023-04-18 16:59 ` [PATCH v5] " Jeff Law
2023-04-18 20:48 ` Patrick O'Neill
2023-04-18 21:04 ` 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=11934bab-4a83-dd3b-7421-a1bf0d3e1439@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=david.abd@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
--cc=patrick@rivosinc.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).