public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.org>
To: gfortran <fortran@gcc.gnu.org>
Subject: Fwd: GCC 11.0.1 Status Report (2021-03-16)
Date: Tue, 16 Mar 2021 15:57:38 +0100	[thread overview]
Message-ID: <c375781e-441c-4b76-553e-ec5f0831f32b@moene.org> (raw)
In-Reply-To: <nycvar.YFH.7.76.2103161218160.17979@zhemvz.fhfr.qr>

For Your Information ...


-------- Forwarded Message --------
Subject: GCC 11.0.1 Status Report (2021-03-16)
Date: Tue, 16 Mar 2021 12:19:20 +0100 (CET)
From: Richard Biener <rguenther@suse.de>
Reply-To: gcc@gcc.gnu.org
To: gcc@gcc.gnu.org
CC: gcc-patches@gcc.gnu.org


Status
======

GCC trunk which eventually will become GCC 11 is still in
regression and documentation fixes only mode (Stage 4).

If history should repeat itself then a first release candidate
of GCC 11 will be released mid April.  For this to happen
we need to resolve the remaining 17 P1 regressions - 8 of which
are classified as target or bootstrap issues.  Please have
a look at the set of P1 (and preferably also P2) regressions
which can be conveniently accessed via the 'Serious regressions'
link on https://gcc.gnu.org


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

Priority          #   Change from last report
--------        ---   -----------------------
P1               17   - 45
P2              288   - 46
P3               37   +  1
P4              192   +  2
P5               24
--------        ---   -----------------------
Total P1-P3     342   - 90
Total		558   - 88


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

https://gcc.gnu.org/pipermail/gcc/2021-January/234703.html

           reply	other threads:[~2021-03-16 14:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <nycvar.YFH.7.76.2103161218160.17979@zhemvz.fhfr.qr>]

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=c375781e-441c-4b76-553e-ec5f0831f32b@moene.org \
    --to=toon@moene.org \
    --cc=fortran@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).