From: Jakub Jelinek <jakub@redhat.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: ewlu@rivosinc.com, gcc-patches@gcc.gnu.org, gnu-toolchain@rivosinc.com
Subject: Re: [gcc-13 backport PATCH] RISC-V: Fix C23 (...) functions returning large aggregates [PR114175]
Date: Thu, 4 Apr 2024 16:37:56 +0200 [thread overview]
Message-ID: <Zg67RAYHzzRdqudN@tucnak> (raw)
In-Reply-To: <mhng-18396bb0-0bd9-4619-a2e1-bccd310afd0e@palmer-ri-x1c9a>
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.
> 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...
Jakub
next prev parent reply other threads:[~2024-04-04 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 20:17 Edwin Lu
2024-04-04 14:28 ` Palmer Dabbelt
2024-04-04 14:37 ` Jakub Jelinek [this message]
2024-04-04 14:40 ` Palmer Dabbelt
2024-04-04 16:28 ` [gcc-13 backport Committed] " Edwin Lu
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=Zg67RAYHzzRdqudN@tucnak \
--to=jakub@redhat.com \
--cc=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.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).