From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 13.0.0 Status Report (2022-10-20), Stage 1 ends Nov 13th
Date: Thu, 20 Oct 2022 08:36:35 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2210200835440.18337@jbgna.fhfr.qr> (raw)
Status
======
The GCC development branch which will become GCC 13 is open for
general development (Stage 1). Stage 1 will end at the end of
November 13th after which we will accept no new features that
have not yet been submitted. Starting with Novemer 14th we
are in a two month general bugfixing period (Stage 3).
I have gone over the set of unpriorized regression bugs that are in
confirmed state, please help updating regressions that are still
UNCONFIRMED and consider fixing bugs that are in your area of
interest. Please make sure to finish and submit features you
want to see included into GCC 13 timely and actively look for
reviewers.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 33 + 33
P2 473 + 102
P3 84 + 7
P4 247 - 6
P5 25 - 1
-------- --- -----------------------
Total P1-P3 590 + 142
Total 862 + 135
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2022-April/238619.html
reply other threads:[~2022-10-20 8:36 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.2210200835440.18337@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).