From: William Seurer <seurer@linux.ibm.com>
To: gcc@gcc.gnu.org
Subject: Re: GCC 12.4 Release Candidate available from gcc.gnu.org
Date: Thu, 13 Jun 2024 17:16:20 -0500 [thread overview]
Message-ID: <fb21ccfd-6f5a-35d1-b4ce-4c50297fa963@linux.ibm.com> (raw)
In-Reply-To: <rp2ssp85-3767-n09r-0n49-94n9r73p3082@fhfr.qr>
On 6/13/24 3:13 AM, Richard Biener via Gcc wrote:
> The first release candidate for GCC 12.4 is available from
>
> https://gcc.gnu.org/pub/gcc/snapshots/12.4.0-RC-20240613/
>
> and shortly its mirrors. It has been generated from git commit
> r12-10557-g6693b1f3929771.
>
> 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, we'd like to release 12.4 on Thursday, June 20th.
I bootstrapped and tested it on power 8 and 9 BE and power 8, 9, and 10
LE and all went well.
next prev parent reply other threads:[~2024-06-13 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 8:13 Richard Biener
2024-06-13 22:16 ` William Seurer [this message]
2024-06-14 6:54 ` Iain Sandoe
2024-06-14 14:45 ` Jonathan Wakely
2024-06-17 6:17 ` Richard Biener
2024-06-17 10:38 ` Jonathan Wakely
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=fb21ccfd-6f5a-35d1-b4ce-4c50297fa963@linux.ibm.com \
--to=seurer@linux.ibm.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).