From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 13.1.1 Status Report (2023-06-23)
Date: Fri, 23 Jun 2023 09:51:31 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2306230950560.4723@jbgna.fhfr.qr> (raw)
Status
======
The gcc-13 branch is open for regression and documentation fixes.
It's time to plan for a GCC 13.2 release which should follow
roughly two to three months after the .1 release. The plan is
to do a release candidate for GCC 13.2 on Thursday, Jul 20th
with the release following a week after that on Thursday, Jul 27th.
That leaves plenty of times to backport regression fixes from trunk.
Please make sure to go over the list of your assigned bugreports and
consider backporting where that seems safe.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 2 + 2
P2 514 + 22
P3 109 + 53
P4 216 - 25
P5 24
-------- --- -----------------------
Total P1-P3 625 + 76
Total 865 + 51
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2023-April/241140.html
reply other threads:[~2023-06-23 9:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.2306230950560.4723@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--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).