From: LIU Hao <lh_mouse@126.com>
To: gcc@gcc.gnu.org
Subject: Re: GCC 12.0.1 Status Report (2022-04-28)
Date: Fri, 29 Apr 2022 21:03:34 +0800 [thread overview]
Message-ID: <045b33a7-5078-de35-1594-8233fed464d0@126.com> (raw)
In-Reply-To: <YmqryWj/O2oiPiWq@tucnak>
[-- Attachment #1.1: Type: text/plain, Size: 682 bytes --]
在 2022-04-28 22:59, Jakub Jelinek via Gcc 写道:
> 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.
>
>
Congrats. I have so far bootstrapped GCC 12.0 on {x86_64,i686}-w64-mingw32 and seen no problems.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2022-04-29 13:03 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
2022-04-29 13:03 ` LIU Hao [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=045b33a7-5078-de35-1594-8233fed464d0@126.com \
--to=lh_mouse@126.com \
--cc=gcc@gcc.gnu.org \
/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).