public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/94042] [10 Regression] Bootstrap fails on ppc-linux-gnu
Date: Tue, 10 Mar 2020 08:51:33 +0000 [thread overview]
Message-ID: <bug-94042-4-9zHTnaDMi0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94042-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94042
--- Comment #43 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #41)
> Ok, the way how we build our compiler is to use:
> ./configure --with-cpu=default32
>
> that should also lead to the ICE. I'm checking that.
So this one crashes for stage3 compiler as well:
$ ./gcc/xgcc -Bgcc /tmp/reduced.ii
/tmp/reduced.ii: In substitution of ‘template<bool <anonymous>, class> struct
__enable_if [with bool <anonymous> = true; <template-parameter-1-2> = _Tp]’:
/tmp/reduced.ii:5:24: required from here
/tmp/reduced.ii:5:24: internal compiler error: Segmentation fault
5 | struct __enable_if<true, _Tp>
| ^~~~~~~~~~~~~~~~~~~~~~
0x10cbb63f crash_signal
../../gcc/toplev.c:328
0x1041f45c contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
../../gcc/tree.h:3391
...
$ cat stage_current
stage3
$ file ./gcc/xgcc
./gcc/xgcc: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.32, with unknown
capability 0x41000000 = 0x11676e75, with unknown capability 0x10000 = 0x90401,
not stripped
next prev parent reply other threads:[~2020-03-10 8:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-94042-4@http.gcc.gnu.org/bugzilla/>
2020-03-09 14:26 ` vmakarov at gcc dot gnu.org
2020-03-09 14:35 ` segher at gcc dot gnu.org
2020-03-09 14:37 ` marxin at gcc dot gnu.org
2020-03-09 14:44 ` segher at gcc dot gnu.org
2020-03-09 14:47 ` segher at gcc dot gnu.org
2020-03-09 14:48 ` segher at gcc dot gnu.org
2020-03-09 14:51 ` marxin at gcc dot gnu.org
2020-03-09 17:52 ` segher at gcc dot gnu.org
2020-03-09 17:53 ` segher at gcc dot gnu.org
2020-03-09 17:54 ` segher at gcc dot gnu.org
2020-03-09 18:09 ` vmakarov at gcc dot gnu.org
2020-03-09 18:15 ` marxin at gcc dot gnu.org
2020-03-09 18:40 ` marxin at gcc dot gnu.org
2020-03-09 21:35 ` segher at gcc dot gnu.org
2020-03-10 8:51 ` marxin at gcc dot gnu.org [this message]
2020-03-10 8:57 ` jakub at gcc dot gnu.org
2020-03-10 9:00 ` marxin at gcc dot gnu.org
2020-03-10 15:13 ` segher at gcc dot gnu.org
2020-03-10 15:16 ` marxin at gcc dot gnu.org
2020-03-13 17:54 ` segher at gcc dot gnu.org
2020-03-13 17:55 ` segher at gcc dot gnu.org
2020-03-15 12:02 ` marxin at gcc dot gnu.org
2020-07-13 11:12 ` segher 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-94042-4-9zHTnaDMi0@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).