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 other/107299] New: [13 regression] Date: Mon, 17 Oct 2022 21:16:03 +0000 [thread overview] Message-ID: <bug-107299-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107299 Bug ID: 107299 Summary: [13 regression] Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: seurer at gcc dot gnu.org Target Milestone: --- g:8efc38347a7444dde3fb173f0f2c59a60b7db53d, r13-3307-g8efc38347a7444 I am seeing this only on a powerpc64 system that has IEE128 enabled in the system compiler. /home/seurer/gcc/git/build/gcc-trunk/./gcc/xgcc -B/home/seurer/gcc/git/build/gcc-trunk/./gcc/ -B/home/seurer/gcc/git/install/gcc-trunk/powerpc64le-unknown-linux-gnu/bin/ -B/home/seurer/gcc/git/install/gcc-trunk/powerpc64le-unknown-linux-gnu/lib/ -isystem /home/seurer/gcc/git/install/gcc-trunk/powerpc64le-unknown-linux-gnu/include -isystem /home/seurer/gcc/git/install/gcc-trunk/powerpc64le-unknown-linux-gnu/sys-include -g -O2 -O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -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-trunk/libgcc -I/home/seurer/gcc/git/gcc-trunk/libgcc/. -I/home/seurer/gcc/git/gcc-trunk/libgcc/../gcc -I/home/seurer/gcc/git/gcc-trunk/libgcc/../include -I/home/seurer/gcc/git/gcc-trunk/libgcc/../libdecnumber/dpd -I/home/seurer/gcc/git/gcc-trunk/libgcc/../libdecnumber -DHAVE_CC_TLS -Wno-type-limits -mvsx -mfloat128 -mno-float128-hardware -mno-gnu-attribute -I/home/seurer/gcc/git/gcc-trunk/libgcc/soft-fp -I/home/seurer/gcc/git/gcc-trunk/libgcc/config/rs6000 -DFLOAT128_HW_INSNS -DFLOAT128_HW_INSNS_ISA3_1 -o _mulkc3.o -MT _mulkc3.o -MD -MP -MF _mulkc3.dep -c /home/seurer/gcc/git/gcc-trunk/libgcc/config/rs6000/_mulkc3.c -fvisibility=hidden -DHIDE_EXPORTS during GIMPLE pass: evrp /home/seurer/gcc/git/gcc-trunk/libgcc/config/rs6000/_mulkc3.c: In function '__mulkc3_sw': /home/seurer/gcc/git/gcc-trunk/libgcc/config/rs6000/_mulkc3.c:97:1: internal compiler error: in fold_stmt, at gimple-range-fold.cc:514 97 | } | ^ 0x11aeaf2f fold_using_range::fold_stmt(vrange&, gimple*, fur_source&, tree_node*) /home/seurer/gcc/git/gcc-trunk/gcc/gimple-range-fold.cc:514 0x11ad78f3 gimple_ranger::fold_range_internal(vrange&, gimple*, tree_node*) /home/seurer/gcc/git/gcc-trunk/gcc/gimple-range.cc:258 0x11ad78f3 gimple_ranger::range_of_stmt(vrange&, gimple*, tree_node*) /home/seurer/gcc/git/gcc-trunk/gcc/gimple-range.cc:319 0x1108419f range_query::value_of_stmt(gimple*, tree_node*) /home/seurer/gcc/git/gcc-trunk/gcc/value-query.cc:135 0x1102e3b7 rvrp_folder::value_of_stmt(gimple*, tree_node*) /home/seurer/gcc/git/gcc-trunk/gcc/tree-vrp.cc:4300 0x10eb64eb substitute_and_fold_dom_walker::before_dom_children(basic_block_def*) /home/seurer/gcc/git/gcc-trunk/gcc/tree-ssa-propagate.cc:816 0x11a9138b dom_walker::walk(basic_block_def*) /home/seurer/gcc/git/gcc-trunk/gcc/domwalk.cc:311 0x10eb4c0f substitute_and_fold_engine::substitute_and_fold(basic_block_def*) /home/seurer/gcc/git/gcc-trunk/gcc/tree-ssa-propagate.cc:987 0x1102065b execute_ranger_vrp(function*, bool) /home/seurer/gcc/git/gcc-trunk/gcc/tree-vrp.cc:4351 commit 8efc38347a7444dde3fb173f0f2c59a60b7db53d (HEAD) Author: Aldy Hernandez <aldyh@redhat.com> Date: Thu Oct 13 17:51:29 2022 +0200 Implement range-op entry for __builtin_copysign.
next reply other threads:[~2022-10-17 21:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-17 21:16 seurer at gcc dot gnu.org [this message] 2022-10-18 5:43 ` [Bug bootstrap/107299] [13 regression] ICE in stage 1 after r13-3307-g8efc38347a7444 aldyh at gcc dot gnu.org 2022-10-18 5:52 ` linkw at gcc dot gnu.org 2022-10-18 7:01 ` aldyh at gcc dot gnu.org 2022-10-18 7:08 ` aldyh at gcc dot gnu.org 2022-10-18 7:26 ` rguenth at gcc dot gnu.org 2022-10-18 7:27 ` rguenth at gcc dot gnu.org 2022-10-18 7:27 ` rguenth at gcc dot gnu.org 2022-10-18 10:13 ` aldyh at gcc dot gnu.org 2022-10-18 10:16 ` aldyh at gcc dot gnu.org 2022-10-26 17:46 ` seurer at gcc dot gnu.org 2023-03-06 22:42 ` cvs-commit at gcc dot gnu.org 2023-03-09 15:10 ` redi at gcc dot gnu.org 2023-03-15 9:40 ` 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-107299-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).