public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Palmer Dabbelt <palmer@rivosinc.com>, richard.guenther@gmail.com
Cc: Patrick O'Neill <patrick@rivosinc.com>,
	gcc-patches@gcc.gnu.org, Kito Cheng <kito.cheng@gmail.com>,
	david.abd@gmail.com, schwab@linux-m68k.org
Subject: Re: [committed] RISCV: Inline subword atomic ops
Date: Wed, 3 May 2023 09:13:23 -0600	[thread overview]
Message-ID: <df144cd6-0355-5372-825e-d69251dd04c5@gmail.com> (raw)
In-Reply-To: <mhng-55a8e3b9-919f-4737-9ac9-52d451e716ab@palmer-ri-x1c9>



On 5/3/23 08:14, Palmer Dabbelt wrote:
> On Wed, 03 May 2023 02:49:41 PDT (-0700), richard.guenther@gmail.com wrote:
>> On Wed, May 3, 2023 at 8:33 AM Jeff Law via Gcc-patches
>> <gcc-patches@gcc.gnu.org> wrote:
>>>
>>>
>>>
>>> On 5/2/23 14:34, Patrick O'Neill wrote:
>>> > Is this OK for a backport to GCC-13 as well?
>>> Let me sync with Richi & Jakub.  They're the release managers and this
>>> doesn't fall under the usual rules for things that can be backported.
>>
>> I would guess that most distros have these patches backported (SUSE has
>> that to both 12 and 13), so it wouldn't make much of a difference.  Since
> 
> That'd be my argument, too.  The distros that don't have this probably 
> have something scarier, like an implicit default to -latomic.
> 
>> this is backend specific and RISCV is neither primary nor secondary
>> it's up to the target maintainer discretion to bend the rules.
> 
> Fair, though we're trying to at least pretend we're playing by the 
> rules... ;)
So the net is let's backport this patch series to gcc-13.

jeff


  reply	other threads:[~2023-05-03 15:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 21:58 [PATCH v4] RISC-V: Add support for inlining subword atomic operations Palmer Dabbelt
2022-09-02 10:08 ` Kito Cheng
2022-10-28 16:55   ` David Abdurachmanov
2022-11-16  3:53     ` Jeff Law
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 [this message]
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=df144cd6-0355-5372-825e-d69251dd04c5@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=david.abd@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kito.cheng@gmail.com \
    --cc=palmer@rivosinc.com \
    --cc=patrick@rivosinc.com \
    --cc=richard.guenther@gmail.com \
    --cc=schwab@linux-m68k.org \
    /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).