From: Richard Biener <rguenther@suse.de>
To: gcc@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: GCC 10.4.1 Status Report (2023-06-23)
Date: Fri, 23 Jun 2023 11:00:26 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2306231059510.4723@jbgna.fhfr.qr> (raw)
Status
======
The gcc-10 branch is open for regression and documentation fixes.
The last release from the branch, GCC 10.5, before it is being
closed is due. There will be a release candidate next week,
Friday, June 30th followed by the actual release a week later
on July 7th.
Please check if you have any important and safe regression fixes
to backport and verify your port is on good shape to build from
the branch so we do not end up with a non-working last release
from that branch.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 0
P2 457 + 16
P3 56 + 11
P4 179 - 27
P5 23 - 1
-------- --- -----------------------
Total P1-P3 513 + 27
Total 715 - 1
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2022-October/239683.html
reply other threads:[~2023-06-23 11:00 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.2306231059510.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).