From: Jakub Jelinek <jakub@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: Richard Biener <rguenther@suse.de>, gcc@gcc.gnu.org
Subject: Re: GCC 10.3 Release Candidate available from gcc.gnu.org
Date: Fri, 2 Apr 2021 09:58:56 +0200 [thread overview]
Message-ID: <20210402075856.GE1179226@tucnak> (raw)
In-Reply-To: <a8bebfd4-20ee-8ea0-1835-c51460565bb0@ubuntu.com>
On Fri, Apr 02, 2021 at 09:37:26AM +0200, Matthias Klose wrote:
> On 4/1/21 2:35 PM, Richard Biener wrote:
> >
> > The first release candidate for GCC 10.3 is available from
> >
> > https://gcc.gnu.org/pub/gcc/snapshots/10.3.0-RC-20210401/
> > ftp://gcc.gnu.org/pub/gcc/snapshots/10.3.0-RC-20210401/
> >
> > and shortly its mirrors. It has been generated from git commit
> > 892024d4af83b258801ff7484bf28f0cf1a1a999.
> >
> > I have so far bootstrapped and tested the release candidate on
> > x86_64-linux. Please test it and report any issues to bugzilla.
>
> with the backport of PR95842, the plugin header install is now broken.
>
> Needs also backporting of 9a83366b62e585cce5577309013a832f895ccdbf
> "Fix up plugin header install".
Cherry-picked now.
Jakub
next prev parent reply other threads:[~2021-04-02 8:00 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
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 [this message]
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=20210402075856.GE1179226@tucnak \
--to=jakub@redhat.com \
--cc=doko@ubuntu.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).