public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: GCC 9.5 Release Candidate available
Date: Mon, 23 May 2022 06:27:51 +0000 (UTC)	[thread overview]
Message-ID: <nycvar.YFH.7.77.849.2205230623430.4278@jbgna.fhfr.qr> (raw)
In-Reply-To: <34E0BB32-AAA5-4BCC-A7D5-E70C8ECBC6D1@sandoe.co.uk>

On Sun, 22 May 2022, Iain Sandoe wrote:

> Hi
> 
> > On 20 May 2022, at 09:02, Richard Biener via Gcc <gcc@gcc.gnu.org> wrote:
> 
> > The first release candidate for GCC 9.5 is available from
> > 
> > https://sourceware.org/pub/gcc/snapshots/9.5.0-RC-20220520/
> > 
> > and shortly its mirrors.  It has been generated from git commit
> > 1bc79c506205b6a5db82897340bdebaaf7ada934.
> > 
> > I have so far bootstrapped and tested the release candidate
> > on x86_64-suse-linux.
> 
> I have bootstrapped (using GCC5.4 on darwin9 and GCC7.5 elsewhere) r9-10192 on:
> i686-darwin9,17
> powerpc-darwin9
> x86_64-darwin10 to 21.
> 
> As, expected (since I was not able to find enough time to do the backports),
> although bootstrap succeeds on darwin21 (macOS 12) the resulting compiler
> is not really usable.  I will have to provide a darwin branch with the necessary
> changes.
> 
> One observation outside of this:
> 
> Several of the testsuite runs hung with cc1 spinning in reload for pr88414.
> I was not really able to correlate exactly with CPU / tuning chosen.
> 
> Pretty sure this is a regression - I do not recall the testsuite hanging (for anything
> other than D) for years.

That's gcc.target/i386/pr88414.c?

Can you be more specific on the target the issue occurs on (so one
can maybe try with a cross?).  Bisecting would be most helpful of
course, if it's some of the recent backports reversion would be
most appropriate at this point.

Thanks,
Richard.

  reply	other threads:[~2022-05-23  6:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  8:02 Richard Biener
2022-05-22  8:43 ` Iain Sandoe
2022-05-23  6:27   ` Richard Biener [this message]
2022-05-23  6:50     ` Iain Sandoe
2022-05-23  7:03       ` Iain Sandoe
2022-05-23 15:30 ` William Seurer
2022-05-25 23:08 ` Andrew Pinski

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=nycvar.YFH.7.77.849.2205230623430.4278@jbgna.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    /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).