From: Iain Sandoe <idsandoe@googlemail.com>
To: gcc@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: GCC 8.5 Release Candidate available from gcc.gnu.org
Date: Sun, 9 May 2021 20:53:00 +0100 [thread overview]
Message-ID: <1BE387DB-FDA2-49DD-8A1D-78ED24A06F11@googlemail.com> (raw)
In-Reply-To: <77766b88-5779-9db8-fde5-528051a9a571@linux.ibm.com>
William Seurer via Gcc <gcc@gcc.gnu.org> wrote:
> On 5/7/21 2:48 PM, Jakub Jelinek via Gcc wrote:
>> The first release candidate for GCC 8.5 is available from
>>
>> https://gcc.gnu.org/pub/gcc/snapshots/8.5.0-RC-20210507/
>> ftp://gcc.gnu.org/pub/gcc/snapshots/8.5.0-RC-20210507
>>
>> and shortly its mirrors. It has been generated from git revision
>> r8-10959-g3488242b9a949ebc55b4a857380f94506f90ff76.
>>
>> I have so far bootstrapped and tested the release candidate on
>> x86_64-linux and i686-linux. Please test it and report any issues to
>> bugzilla.
>>
>> If all goes well, I'd like to release 8.5 on Friday, May 14th.
> I bootstrapped and tested on powerpc64 power 7 and 8 BE and power 8, 9,
> and 10 LE and saw nothing unexpected.
I bootstrapped and tested on i686-darwin8, 9, 10, powerpc-darwin9,
x86_64-darwin10..20.
Test results are as expected - notably:
* Darwin20 bootstraps OK, but it is not very usable without further patches (which I will push somewhere once the release is done).
* Sanitizer support is poor on earlier systems without use of llvm-symbolizer (the installed atos program does not handle the sanitizer output well).
(nothing here that’s a show-stopper, but downstream users are advised to
make suitable amendments/installations)
thanks
Iain
prev parent reply other threads:[~2021-05-09 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 19:48 Jakub Jelinek
2021-05-07 23:17 ` William Seurer
2021-05-09 19:53 ` 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=1BE387DB-FDA2-49DD-8A1D-78ED24A06F11@googlemail.com \
--to=idsandoe@googlemail.com \
--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).