public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 12.1.1 Status Report (2022-07-27)
Date: Wed, 27 Jul 2022 10:16:28 +0000 (UTC)	[thread overview]
Message-ID: <nycvar.YFH.7.77.849.2207271015500.6583@jbgna.fhfr.qr> (raw)


Status
======

The gcc-12 branch is open for regression and documentation fixes.

It is time for a GCC 12.2 release, we are comparatively late with it
already.  The plan is to create a GCC 12.2 release candidate on
August 12th which should give plenty of time to backport or implement
important regression fixes.

Please make sure your primary and secondary targets are in good
shape for this release.


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

Priority          #   Change from last report
--------        ---   -----------------------
P1              0      
P2              429   +  62
P3              63    -  22
P4              240   -   8
P5              25    -   1
--------        ---   -----------------------
Total P1-P3     492   +  40
Total		757   +  31


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

https://gcc.gnu.org/pipermail/gcc/2022-May/238654.html

                 reply	other threads:[~2022-07-27 10:16 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.2207271015500.6583@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).