From: Jeff Law <jeffreyalaw@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 12.0.1 Status Report (2022-04-28)
Date: Thu, 28 Apr 2022 09:30:27 -0600 [thread overview]
Message-ID: <f7f6150d-77e4-bd0e-731f-b7dc1eb3f2ca@gmail.com> (raw)
In-Reply-To: <YmqywZaKfNx9c2p7@tucnak>
On 4/28/2022 9:29 AM, Jakub Jelinek wrote:
> On Thu, Apr 28, 2022 at 09:25:43AM -0600, Jeff Law via Gcc wrote:
>> On 4/28/2022 8:59 AM, Jakub Jelinek via Gcc wrote:
>>> Status
>>> ======
>>>
>>> We have reached zero P1 regressions today and releases/gcc-12 branch has
>>> been created. GCC 12.1-rc1 will be built likely tomorrow.
>>> The branch is now frozen for blocking regressions and documentation
>>> fixes only, all changes to the branch require a RM approval now.
>>>
>>> If no show stoppers appear, we'd like to release 12.1 late next week,
>>> or soon after that, if any important issues are discovered and
>>> fixed, rc2 could be released next week.
>> Do you want me to adjust the testsuite so that we handle the new linker
>> warnings for executable stacks better? The situation now isn't ideal in
>> that we're showing spurious regressions if we use the development binutils
>> bits.
>>
>> My pending change backs out my change to gcc.dg/lto/pr04157_0.c and instead
>> prunes the new warnings out in prune.exp. I was waiting on validation of a
>> couple targets in my tester which completed yesterday.
> Ok if committed today. With the RC we are mainly waiting on PR105417 fix.
I'll push it shortly.
jeff
next prev parent reply other threads:[~2022-04-28 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 14:59 Jakub Jelinek
2022-04-28 15:25 ` Jeff Law
2022-04-28 15:29 ` Jakub Jelinek
2022-04-28 15:30 ` Jeff Law [this message]
2022-04-29 13:03 ` LIU Hao
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=f7f6150d-77e4-bd0e-731f-b7dc1eb3f2ca@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.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).