From: Richard Biener <rguenther@suse.de>
To: Martin Uecker <uecker@tugraz.at>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Re: GCC 12.2.1 Status Report (2023-05-02), branch frozen for release
Date: Thu, 4 May 2023 10:04:11 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2305041003260.4466@jbgna.fhfr.qr> (raw)
In-Reply-To: <05d57b8b887a55a3e3e8ecb8fb4afc7d6b793175.camel@tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Thu, 4 May 2023, Martin Uecker wrote:
> Am Donnerstag, dem 04.05.2023 um 09:53 +0000 schrieb Richard Biener:
> > On Thu, 4 May 2023, Martin Uecker wrote:
> >
> > >
> > > Can I please get permission for fixing this ICE?
> > >
> > > https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616221.html
> >
> > Please wait until after the branch is unfrozen. When patches were
> > approved for trunk and they are regressions there's no further
> > approval needed to backport them (but of course bootstrap & testing
> > is required on the branches backported to).
>
> Ok, thanks - good to know! Next time I just push important
> fixes for regressions approved for trunk. But does this mean
> we need to wait for about a year to get this fix into 12?
> This would be a bit unfortunate for this problem I think.
You have to wait about a year to have a released compiler based on 12
with the fix, yes. But most people use snapshots from the respective
branches anyway.
Richard.
prev parent reply other threads:[~2023-05-04 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 6:54 Richard Biener
2023-05-04 6:16 ` Martin Uecker
2023-05-04 9:53 ` Richard Biener
2023-05-04 9:58 ` Martin Uecker
2023-05-04 10:04 ` Richard Biener [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=nycvar.YFH.7.77.849.2305041003260.4466@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=uecker@tugraz.at \
/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).