public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/99920] [10 regression] ICE building gcc 10 on power 7 BE
Date: Tue, 06 Apr 2021 16:04:58 +0000 [thread overview]
Message-ID: <bug-99920-4-UryQm1LuCf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99920-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99920
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-04-06
Resolution|INVALID |---
Status|RESOLVED |REOPENED
Ever confirmed|0 |1
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If the problematic older system gcc was 4.1+, can you please bisect among *.o
files compiled by the system gcc?
If the ICE is with the stage1 gcc when building stage1 libgcc, then
the suspected TUs could be gimple-ssa-store-merging.o or fold-const.o, would be
nice to start with those.
I.e. build again with your older system gcc, verify it fails, make a copy of
those two *.o files, rebuild them with gcc 8.x, make cc1 cc1plus and verify it
doesn't ICE anymore.
next prev parent reply other threads:[~2021-04-06 16:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 22:28 [Bug bootstrap/99920] New: " seurer at gcc dot gnu.org
2021-04-06 7:29 ` [Bug bootstrap/99920] " rguenth at gcc dot gnu.org
2021-04-06 7:31 ` jakub at gcc dot gnu.org
2021-04-06 9:24 ` jakub at gcc dot gnu.org
2021-04-06 13:02 ` seurer at gcc dot gnu.org
2021-04-06 13:09 ` rguenther at suse dot de
2021-04-06 13:30 ` jakub at gcc dot gnu.org
2021-04-06 16:04 ` jakub at gcc dot gnu.org [this message]
2021-04-06 17:11 ` seurer at gcc dot gnu.org
2021-04-06 17:40 ` seurer at gcc dot gnu.org
2021-04-07 8:13 ` jakub at gcc dot gnu.org
2021-04-07 8:26 ` rguenther at suse dot de
2021-04-07 17:57 ` seurer at gcc dot gnu.org
2021-04-07 18:56 ` jakub at gcc dot gnu.org
2021-04-08 8:55 ` rguenth at gcc dot gnu.org
2021-04-08 10:53 ` rguenth at gcc dot gnu.org
2021-04-08 11:19 ` rguenth at gcc dot gnu.org
2021-04-08 11:52 ` rguenth at gcc dot gnu.org
2021-04-08 11:53 ` rguenth at gcc dot gnu.org
2021-04-08 12:02 ` rguenth at gcc dot gnu.org
2021-04-08 14:15 ` seurer at gcc dot gnu.org
2022-01-11 11:10 ` [Bug bootstrap/99920] [10 regression] ICE building gcc 10 on power 7 BE with GCC 4.3.4 (SUSE) host compiler rguenth at gcc dot gnu.org
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=bug-99920-4-UryQm1LuCf@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).