public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Jonathan Wakely via Gcc <gcc@gcc.gnu.org>,
	Iain Sandoe <idsandoe@googlemail.com>,
	 Jonathan Wakely <jwakely@redhat.com>,
	Richard Biener <rguenther@suse.de>
Subject: Re: GCC 10.3 Release Candidate available from gcc.gnu.org
Date: Thu, 1 Apr 2021 21:31:29 +0100	[thread overview]
Message-ID: <CAH6eHdSyGNAsJCg5mEWGm7GjPit-MRyj4TbT7pyzV_Bq9m1ufw@mail.gmail.com> (raw)
In-Reply-To: <A67D057D-5187-4A21-B38E-36F7D2AFA293@gmail.com>

On Thu, 1 Apr 2021 at 21:08, Richard Biener wrote:
>
> On April 1, 2021 9:49:19 PM GMT+02:00, Jonathan Wakely via Gcc <gcc@gcc.gnu.org> wrote:
> >On Thu, 1 Apr 2021 at 20:23, Iain Sandoe wrote:
> >>
> >> Richard Biener <rguenther@suse.de> wrote:
> >>
> >> > On April 1, 2021 4:08:21 PM GMT+02:00, Eric Botcazou
> >> > <botcazou@adacore.com> wrote:
> >> >>> I have so far bootstrapped and tested the release candidate on
> >> >>> x86_64-linux.  Please test it and report any issues to bugzilla.
> >>
> >> On x86 Darwin, a lot of new libstdc++ experimental/filesystem fails.
> >>
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99875
> >
> >I missed a backport, this is needed for gcc-10 branch:
> >https://gcc.gnu.org/cgi-bin/gcc-gitref.cgi?r=r11-7239
> >Only affects the testsuite, but in a util header that is used by lots
> >of tests.
> >
> >I'll wait for RM approval before pushing the backport.
>
> This is OK.

Pushed, thanks.

  reply	other threads:[~2021-04-01 20:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 12:35 Richard Biener
2021-04-01 14:08 ` Eric Botcazou
2021-04-01 17:15   ` Richard Biener
2021-04-01 19:21     ` Iain Sandoe
2021-04-01 19:49       ` Jonathan Wakely
2021-04-01 20:07         ` Richard Biener
2021-04-01 20:31           ` Jonathan Wakely [this message]
2021-04-01 20:59         ` Jakub Jelinek
2021-04-01 21:59 ` William Seurer
2021-04-02  7:37 ` Matthias Klose
2021-04-02  7:58   ` Jakub Jelinek
2021-04-02 23:51 ` Richard Copley
2021-04-03 10:34   ` Jonathan Wakely
2021-04-03 12:25     ` Iain Sandoe
2021-04-03 21:12       ` Richard Copley
2021-04-04 11:40         ` Richard Copley
2021-04-04 19:29           ` Jonathan Wakely
2021-04-04 20:26 ` Christophe Lyon
2021-04-05  6:34   ` Richard Biener

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=CAH6eHdSyGNAsJCg5mEWGm7GjPit-MRyj4TbT7pyzV_Bq9m1ufw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=idsandoe@googlemail.com \
    --cc=jwakely@redhat.com \
    --cc=rguenther@suse.de \
    --cc=richard.guenther@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).