public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/99920] New: [10 regression] ICE building gcc 10 on power 7 BE Date: Mon, 05 Apr 2021 22:28:28 +0000 [thread overview] Message-ID: <bug-99920-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99920 Bug ID: 99920 Summary: [10 regression] ICE building gcc 10 on power 7 BE Product: gcc Version: 10.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:6aa75d3740c309aeead9c430a6779f4a347f4403, r10-9659 This occurs at this commit but it is not the source of it (I am still looking). Configure used: /home/seurer/gcc/git/gcc-10-test/configure --enable-languages=c,fortran,c++ --with-cpu=power7 --enable-bootstrap --enable-multilib A whole bunch of ICEs like the following occur when building gcc on power 7 BE. It does not occurs on power 8 BE. /home/seurer/gcc/git/build/gcc-10-test/./gcc/xgcc -B/home/seurer/gcc/git/build/gcc-10-test/./gcc/ -B/home/seurer/gcc/git/install/gcc-10-test/powerpc64-unknown-linux-gnu/bin/ -B/home/seurer/gcc/git/install/gcc-10-test/powerpc64-unknown-linux-gnu/lib/ -isystem /home/seurer/gcc/git/install/gcc-10-test/powerpc64-unknown-linux-gnu/include -isystem /home/seurer/gcc/git/install/gcc-10-test/powerpc64-unknown-linux-gnu/sys-include -fno-checking -g -O2 -m32 -O2 -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wno-format -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -mlong-double-128 -mno-minimal-toc -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -fPIC -mlong-double-128 -mno-minimal-toc -I. -I. -I../../.././gcc -I/home/seurer/gcc/git/gcc-10-test/libgcc -I/home/seurer/gcc/git/gcc-10-test/libgcc/. -I/home/seurer/gcc/git/gcc-10-test/libgcc/../gcc -I/home/seurer/gcc/git/gcc-10-test/libgcc/../include -I/home/seurer/gcc/git/gcc-10-test/libgcc/../libdecnumber/dpd -I/home/seurer/gcc/git/gcc-10-test/libgcc/../libdecnumber -DHAVE_CC_TLS -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c /home/seurer/gcc/git/gcc-10-test/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS during GIMPLE pass: store-merging In file included from /home/seurer/gcc/git/gcc-10-test/libgcc/libgcc2.c:56: /home/seurer/gcc/git/gcc-10-test/libgcc/libgcc2.c: In function '__muldi3': /home/seurer/gcc/git/gcc-10-test/libgcc/libgcc2.h:219:20: internal compiler error: Segmentation fault 219 | #define __NDW(a,b) __ ## a ## di ## b | ^~ /home/seurer/gcc/git/gcc-10-test/libgcc/libgcc2.h:273:18: note: in expansion of macro '__NDW' 273 | #define __muldi3 __NDW(mul,3) | ^~~~~ /home/seurer/gcc/git/gcc-10-test/libgcc/libgcc2.c:548:1: note: in expansion of macro '__muldi3' 548 | __muldi3 (DWtype u, DWtype v) | ^~~~~~~~ 0x111d588f crash_signal /home/seurer/gcc/git/gcc-10-test/gcc/toplev.c:328 0x125d1930 trim_filename(char const*) /home/seurer/gcc/git/gcc-10-test/gcc/diagnostic.c:1223 0x125d4273 fancy_abort(char const*, int, char const*) /home/seurer/gcc/git/gcc-10-test/gcc/diagnostic.c:1778 0x10a76dab operand_compare::hash_operand(tree_node const*, inchash::hash&, unsigned int) /home/seurer/gcc/git/gcc-10-test/gcc/fold-const.c:3768 0x10a7766b inchash::add_expr(tree_node const*, inchash::hash&, unsigned int) /home/seurer/gcc/git/gcc-10-test/gcc/fold-const.c:3919 0x1122c2af iterative_hash_expr /home/seurer/gcc/git/gcc-10-test/gcc/tree.h:5207 0x11232c77 tree_operand_hash::hash(tree_node* const&) /home/seurer/gcc/git/gcc-10-test/gcc/tree-hash-traits.h:34 0x1231a2af hash /home/seurer/gcc/git/gcc-10-test/gcc/hash-map-traits.h:50 0x1231b97b get /home/seurer/gcc/git/gcc-10-test/gcc/hash-map.h:184 0x1232fbaf process_store /home/seurer/gcc/git/gcc-10-test/gcc/gimple-ssa-store-merging.c:4883 0x123304a7 execute /home/seurer/gcc/git/gcc-10-test/gcc/gimple-ssa-store-merging.c:5040
next reply other threads:[~2021-04-05 22:28 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-05 22:28 seurer at gcc dot gnu.org [this message] 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 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@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: linkBe 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).