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 8.0.0 Status Report (2018-01-15), Trunk in Regression and Documentation fixes only mode
Date: Mon, 15 Jan 2018 08:21:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1801150920260.32271@zhemvz.fhfr.qr> (raw)


Status
======

GCC 8 is in regression and documentation fixes stage now similar as if
trunk was a release branch.

We're still in pretty bad shape regression-wise.  Please also take
the opportunity to check the state of your favorite host/target
combination to make sure building and testing works appropriately.


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

Priority          #   Change from last report
--------        ---   -----------------------
P1               36   +  27
P2              133   -   1
P3               57   -  51
P4		158   -   3
P5		 27
--------        ---   -----------------------
Total P1-P3     226   -  25
Total		411   -  28


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

https://gcc.gnu.org/ml/gcc/2018-01/msg00033.html

             reply	other threads:[~2018-01-15  8:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15  8:21 Richard Biener [this message]
2018-01-16 12:50 ` Segher Boessenkool
2018-01-16 17:11   ` Joseph Myers
2018-01-17 17:56   ` Segher Boessenkool
2018-01-16 19:20 ` Andrew Roberts
2018-01-17  8:20   ` Richard Biener
2018-01-26 14:22     ` Rainer Orth
2018-01-26 18:56       ` Andrew Roberts
2018-01-27 14:38         ` Rainer Orth
2018-02-06  9:22       ` Rainer Orth
2018-02-06  9:49     ` Matthias Klose
2018-02-06 16:14       ` Vincent Lefevre
2018-02-06 16:28         ` Vincent Lefevre
2018-02-06 17:34           ` Joseph Myers
2018-02-06 21:59             ` Vincent Lefevre
2018-02-06 17:32         ` Joseph Myers
2018-02-06 21:48           ` Vincent Lefevre

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=alpine.LSU.2.20.1801150920260.32271@zhemvz.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).