From: Iain Sandoe <iain@sandoe.co.uk>
To: Richard Biener <rguenther@suse.de>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: GCC 9.5 Release Candidate available
Date: Mon, 23 May 2022 07:50:50 +0100 [thread overview]
Message-ID: <55B5D800-2EE5-4E67-807E-9633402457E5@sandoe.co.uk> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2205230623430.4278@jbgna.fhfr.qr>
Hi Richard,
> On 23 May 2022, at 07:27, Richard Biener <rguenther@suse.de> wrote:
>
> 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.
several cases, here’s the most modern with an m32 multilib:
Configured with: /src-local/gcc-git-9/configure --prefix=/opt/iains/x86_64-apple-darwin17/gcc-9-wip --build=x86_64-apple-darwin17 --with-sysroot=/Library//Developer/CommandLineTools/SDKs/MacOSX.sdk --with-as=/XC/9.4/usr/bin/as --with-ld=/XC/9.4/usr/bin/ld --enable-languages=all CC=x86_64-apple-darwin17-gcc CXX=x86_64-apple-darwin17-g++
log info:
[ note the m64 multilib, also emits the diagnostic, but it does not appear to spin. ]
/scratch/10-13-his/gcc-9-wip/gcc/xgcc -B/scratch/10-13-his/gcc-9-wip/gcc/ /src-local/gcc-git-9/gcc/testsuite/gcc.target/i386/pr88414.c -m32 -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers -fdiagnostics-color=never -O1 -ftrapv -S -o pr88414.s
/src-local/gcc-git-9/gcc/testsuite/gcc.target/i386/pr88414.c: In function 'foo':
/src-local/gcc-git-9/gcc/testsuite/gcc.target/i386/pr88414.c:15:7: error: 'asm' operand has impossible constraints
got a INT signal, interrupted by user // (manually killed it)
Iain
next prev parent reply other threads:[~2022-05-23 6:50 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
2022-05-23 6:50 ` Iain Sandoe [this message]
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=55B5D800-2EE5-4E67-807E-9633402457E5@sandoe.co.uk \
--to=iain@sandoe.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).