From: Jakub Jelinek <jakub@redhat.com>
To: gcc@gcc.gnu.org
Subject: GCC 10.4 Release Candidate available from gcc.gnu.org
Date: Tue, 21 Jun 2022 13:33:43 +0200 [thread overview]
Message-ID: <YrGsl3KLpd8G3ZdX@tucnak> (raw)
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.
next reply other threads:[~2022-06-21 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 11:33 Jakub Jelinek [this message]
2022-06-21 19:49 ` William Seurer
2022-06-23 8:04 ` Iain Sandoe
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=YrGsl3KLpd8G3ZdX@tucnak \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).