public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* GCC 12.0.0 Status Report (2022-01-10), Stage 3 ends Jan 16th
@ 2022-01-10 11:55 Richard Biener
  0 siblings, 0 replies; only message in thread
From: Richard Biener @ 2022-01-10 11:55 UTC (permalink / raw)
  To: gcc; +Cc: gcc-patches, fortran

Status
======

The GCC development branch is open for general bugfixing (Stage 3)
and will transition to regression and documentation fixing only
(Stage 4) on the end of Jan 16th.

Take the quality data below with a big grain of salt - most of the
new P3 classified bugs will become P1 or P2 (generally every
regression against GCC 11 is to be considered P1 if it concerns
primary or secondary platforms).


Quality Data
============

Priority          #   Change from last report
--------        ---   -----------------------
P1               30   -  4
P2              307   +  1
P3              279   + 42
P4              220   + 13
P5               25
--------        ---   -----------------------
Total P1-P3     616   + 39
Total		861   + 52


Previous Report
===============

https://gcc.gnu.org/pipermail/gcc/2021-November/237741.html

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-01-10 11:55 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-10 11:55 GCC 12.0.0 Status Report (2022-01-10), Stage 3 ends Jan 16th Richard Biener

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).