From: Jakub Jelinek <jakub@redhat.com>
To: gcc@gcc.gnu.org
Subject: GCC 15.0.0 Status Report (2024-04-26)
Date: Fri, 26 Apr 2024 13:03:31 +0200 [thread overview]
Message-ID: <ZiuKA30Agt2me0Tz@tucnak> (raw)
Status
======
The trunk has branched for the GCC 14 release and is now open
again for general development, stage 1. Please consider not
disrupting it too much during the RC phase of GCC 14 so it
is possible to test important fixes for 14.1 on it.
Quality Data
============
Priority # Change from last report
-------- --- -----------------------
P1 6 - 8
P2 607 + 101
P3 58 - 186
P4 219 - 9
P5 25 - 1
-------- --- -----------------------
Total P1-P3 671 - 93
Total 915 - 103
Previous Report
===============
https://gcc.gnu.org/pipermail/gcc/2024-March/243407.html
reply other threads:[~2024-04-26 11:03 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=ZiuKA30Agt2me0Tz@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).