From: Jakub Jelinek <jakub@redhat.com>
To: Martin Sebor <msebor@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 9.2 Status Report (2019-08-05), branch frozen for release
Date: Tue, 06 Aug 2019 07:17:00 -0000 [thread overview]
Message-ID: <20190806071704.GY2726@tucnak> (raw)
In-Reply-To: <ebc2e9e4-0045-5f19-648a-e7ef807f471d@gmail.com>
On Mon, Aug 05, 2019 at 11:03:02AM -0600, Martin Sebor wrote:
> On 8/5/19 7:21 AM, Jakub Jelinek wrote:
> > Status
> > ======
> >
> > The first 9.2 release candidate has been released.
> > The GCC 9 branch is frozen for preparation of the GCC 9.2 release.
> > All changes to the branch now require release manager approval.
>
> Can I get an approval to backport the fix for pr90947 - [9 Regression]
> Simple lookup table of array of strings is miscompiled​?
That would require another rc. Unless we are forced to do it anyway for
other more urgent reasons, I'd prefer to defer for 9.3, you can test now but
commit after the release.
Jakub
next prev parent reply other threads:[~2019-08-06 7:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 13:22 Jakub Jelinek
2019-08-05 17:03 ` Martin Sebor
2019-08-06 7:17 ` Jakub Jelinek [this message]
2019-08-08 14:49 Tom Honermann
2019-08-08 15:04 ` Jakub Jelinek
2019-08-08 15:57 ` Tom Honermann
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=20190806071704.GY2726@tucnak \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=msebor@gmail.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).