From: Richard Copley <rcopley@gmail.com>
To: Richard Biener <rguenther@suse.de>, gcc@gcc.gnu.org
Subject: Re: GCC 10.3 Release Candidate available from gcc.gnu.org
Date: Sat, 3 Apr 2021 00:51:30 +0100 [thread overview]
Message-ID: <e1f2f1a5-cf0d-7e8f-fc0d-ce49932d8602@gmail.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2104011433080.17979@zhemvz.fhfr.qr>
On 01/04/2021 13:35, 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.
>
> If all goes well, I'd like to release 10.3 on Thursday, April 8th.
>
On Windows, linking two C++ translation units that both #include
<coroutine> results in errors about multiple definition of the weak
function __dummy_resume_destroy. This can be avoided by cherry-picking
commit 94fd05f1f76faca9dc9033b55d44c960155d38e9 [PR 95917].
next prev parent reply other threads:[~2021-04-02 23:51 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
2021-04-02 23:51 ` Richard Copley [this message]
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=e1f2f1a5-cf0d-7e8f-fc0d-ce49932d8602@gmail.com \
--to=rcopley@gmail.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).