From: Jakub Jelinek <jakub@redhat.com>
To: gcc@gcc.gnu.org
Subject: GCC 10.3.1 Status Report (2022-06-14)
Date: Tue, 14 Jun 2022 18:57:25 +0200 [thread overview]
Message-ID: <Yqi99fJC1VByPBeM@tucnak> (raw)
Status
======
The GCC 10 branch is in regression and documentation fixing mode.
After the release of GCC 9.5 it's time to do another release
from the 10 branch - GCC 10.4. I will do a GCC 10.4 release candidate
next week, June 21st, followed by the release a week after that
if no serious problems arise.
If you have pending backports, please commit them to GCC 10 branch
this week or on Monday next week. In particular I'd like to see
backport of Honza's PR105739 fix and I'll need to backport PR105732
because it is a P1.
It's also a very good point in time to ensure the branch still builds
and has reasonable testresults for the target you maintain.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 1 + 1
P2 407 + 81
P3 52 + 21
P4 204 + 26
P5 24 + 1
-------- --- -----------------------
Total P1-P3 460 + 103
Total 688 + 130
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2021-April/235360.html
reply other threads:[~2022-06-14 16:57 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=Yqi99fJC1VByPBeM@tucnak \
--to=jakub@redhat.com \
--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).