public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: GCC 9.3 Status Report (2020-03-05)
Date: Fri, 06 Mar 2020 12:48:00 -0000	[thread overview]
Message-ID: <20200306124751.GK2156@tucnak> (raw)
In-Reply-To: <CAH6eHdRuEADKBSZ=_ADVSQGZtNNbo8j5CT7w-AzUrKB91jba+A@mail.gmail.com>

On Fri, Mar 06, 2020 at 12:35:09PM +0000, Jonathan Wakely wrote:
> > The GCC 9 branch is now frozen for blocking regressions and documentation
> > fixes only, all changes to the branch require a RM approval now.
> 
> I'd also like to backport this one:
> https://gcc.gnu.org/ml/gcc-patches/2020-03/msg00360.html
> 
> It only affects the testsuite (and only for *-*-mingw* targets), but
> ensures we don't get FAILs caused by the tests hitting a different
> bug.
> 
> Fixing that other bug will happen for 9.4, but we can avoid the
> failures with a small tweak to the tests, so they still verify what
> was intended. On the other hand, some failing tests won't actually
> hurt the quality of the 9.3 release, so it's not important.

I think this isn't urgent enough and can wait for 9.4.  We don't guarantee
zero FAILs...

	Jakub

  reply	other threads:[~2020-03-06 12:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-05 20:23 Jakub Jelinek
2020-03-06 12:12 ` Jonathan Wakely
2020-03-06 12:18   ` Jakub Jelinek
2020-03-06 12:27     ` Jonathan Wakely
2020-03-06 12:35 ` Jonathan Wakely
2020-03-06 12:48   ` Jakub Jelinek [this message]
2020-03-06 14:15 ` Richard Earnshaw

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=20200306124751.GK2156@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    /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).