From: Iain Sandoe <iain@sandoe.co.uk>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: GCC 10.4 Release Candidate available from gcc.gnu.org
Date: Thu, 23 Jun 2022 09:04:56 +0100 [thread overview]
Message-ID: <039D9A41-F70C-4366-AF91-BC45DF42C511@sandoe.co.uk> (raw)
In-Reply-To: <YrGsl3KLpd8G3ZdX@tucnak>
Hi Jakub,
> On 21 Jun 2022, at 12:33, Jakub Jelinek via Gcc <gcc@gcc.gnu.org> wrote:
>
> The first release candidate for GCC 10.4 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/10.4.0-RC-20220621/
> ftp://gcc.gnu.org/pub/gcc/snapshots/10.4.0-RC-20220621/
>
> and shortly its mirrors. It has been generated from git commit
> r10-10862-g3c390f4ad27c3d79fd1817276a6d3217fd9bfb51.
>
> 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.4 on Tuesday, June 28th.
>
I bootstrapped and tested on i686, powerpc and x86_64 Darwin
from darwin9 to darwin21 (archs as appropriate) - all supported
languages - no new issues seen. I also checked that bootstrap
worked with Apple gcc-4.2.1 on darwin9, 10 and with clang 3.4
on darwin12
Iain
prev parent reply other threads:[~2022-06-23 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 11:33 Jakub Jelinek
2022-06-21 19:49 ` William Seurer
2022-06-23 8:04 ` Iain Sandoe [this message]
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=039D9A41-F70C-4366-AF91-BC45DF42C511@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.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).