public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Edwin Lu <ewlu@rivosinc.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, jakub@redhat.com
Cc: gcc-patches@gcc.gnu.org, gnu-toolchain@rivosinc.com
Subject: Re: [gcc-13 backport Committed] RISC-V: Fix C23 (...) functions returning large aggregates [PR114175]
Date: Thu, 4 Apr 2024 09:28:25 -0700	[thread overview]
Message-ID: <85d6736d-a392-4fab-b6b3-ab8700d75759@rivosinc.com> (raw)
In-Reply-To: <mhng-5cd8ffed-4ce6-47da-83fe-e337e834f97a@palmer-ri-x1c9a>


On 4/4/2024 7:40 AM, Palmer Dabbelt wrote:
> On Thu, 04 Apr 2024 07:37:56 PDT (-0700), jakub@redhat.com wrote:
>> On Thu, Apr 04, 2024 at 07:28:40AM -0700, Palmer Dabbelt wrote:
>>> I'm not sure if we need release maintainer approval,
>>
>> For cherry-picking one's own non-risky bugfixes for regression or
>> documentation bugs from trunk to release branches no special approval
>> is needed, or maintainer of the corresponding code can approve that,
>> release manager approval is only needed when a branch is frozen before a
>> release.
>
> Ya, I'm just never sure when the branch is frozen...
>
>>> all I can find is the
>>> 13.2.1 status report saying 13.3 is expected in the spring
>>> <https://inbox.sourceware.org/gcc/ZMJeq%2FY5SN+7i8a+@tucnak/>.  My 
>>> allergies
>>> certainly indicate it's spring, but that's kind of a wide time 
>>> window...
>>>
>>> Maybe Jakub knows?
>>
>> Most likely some short time after 14.1 is released, so that one can 
>> still
>> cherry-pick whatever was fixed on the 14 branch and there is time for 
>> those
>> cherry-picks and testing.
>> https://gcc.gnu.org/releases.html#timeline gives some hints...
>
> OK, so sounds like it's not frozen now and Edwin's OK to commit this 
> on the 13 branch.  Thanks.
>
>>
>>     Jakub

Thanks for the clarifications! Committed!

Edwin


      reply	other threads:[~2024-04-04 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 20:17 [gcc-13 backport PATCH] " Edwin Lu
2024-04-04 14:28 ` Palmer Dabbelt
2024-04-04 14:37   ` Jakub Jelinek
2024-04-04 14:40     ` Palmer Dabbelt
2024-04-04 16:28       ` Edwin Lu [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=85d6736d-a392-4fab-b6b3-ab8700d75759@rivosinc.com \
    --to=ewlu@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gnu-toolchain@rivosinc.com \
    --cc=jakub@redhat.com \
    --cc=palmer@dabbelt.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).