public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/107299] [13 regression] ICE in stage 1 after r13-3307-g8efc38347a7444 Date: Thu, 09 Mar 2023 15:10:04 +0000 [thread overview] Message-ID: <bug-107299-4-zZYm7RJTAz@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107299-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107299 --- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> --- I can build trunk without --enable-checking=release now, but I get some FAILs in the libstdc++ testsuite: during GIMPLE pass: threadfull /home/test/src/gcc/libstdc++-v3/testsuite/20_util/to_chars/float128_c++23.cc: In function 'void test(std::chars_format)': /home/test/src/gcc/libstdc++-v3/testsuite/20_util/to_chars/float128_c++23.cc:34: internal compiler error: in fold_stmt, at gimple-range-fold.cc:522 0x11ed1b03 fold_using_range::fold_stmt(vrange&, gimple*, fur_source&, tree_node*) /home/test/src/gcc/gcc/gimple-range-fold.cc:522 0x11ebd503 gimple_ranger::fold_range_internal(vrange&, gimple*, tree_node*) /home/test/src/gcc/gcc/gimple-range.cc:257 0x11ebd503 gimple_ranger::range_of_stmt(vrange&, gimple*, tree_node*) /home/test/src/gcc/gcc/gimple-range.cc:318 0x11ebb64f gimple_ranger::range_on_entry(vrange&, basic_block_def*, tree_node*) /home/test/src/gcc/gcc/gimple-range.cc:153 0x112368c3 path_range_query::range_on_path_entry(vrange&, tree_node*) /home/test/src/gcc/gcc/gimple-range-path.cc:160 0x11238063 path_range_query::internal_range_of_expr(vrange&, tree_node*, gimple*) /home/test/src/gcc/gcc/gimple-range-path.cc:176 0x112382b7 path_range_query::range_of_expr(vrange&, tree_node*, gimple*) /home/test/src/gcc/gcc/gimple-range-path.cc:202 0x11ecb723 fur_stmt::get_operand(vrange&, tree_node*) /home/test/src/gcc/gcc/gimple-range-fold.cc:157 0x11ecf48f fold_using_range::range_of_range_op(vrange&, gimple_range_op_handler&, fur_source&) /home/test/src/gcc/gcc/gimple-range-fold.cc:577 0x11ed1a03 fold_using_range::fold_stmt(vrange&, gimple*, fur_source&, tree_node*) /home/test/src/gcc/gcc/gimple-range-fold.cc:489 0x11237733 path_range_query::range_of_stmt(vrange&, gimple*, tree_node*) /home/test/src/gcc/gcc/gimple-range-path.cc:721 0x112f0db3 back_threader::find_taken_edge_cond(vec<basic_block_def*, va_heap, vl_ptr> const&, gcond*) /home/test/src/gcc/gcc/tree-ssa-threadbackward.cc:325 0x112f1087 back_threader::maybe_register_path(back_threader_profitability&) /home/test/src/gcc/gcc/tree-ssa-threadbackward.cc:248 0x112f1503 back_threader::find_paths_to_names(basic_block_def*, bitmap_head*, unsigned int, back_threader_profitability&) /home/test/src/gcc/gcc/tree-ssa-threadbackward.cc:371 0x112f1b27 back_threader::find_paths_to_names(basic_block_def*, bitmap_head*, unsigned int, back_threader_profitability&) /home/test/src/gcc/gcc/tree-ssa-threadbackward.cc:479 0x112f282b back_threader::maybe_thread_block(basic_block_def*) /home/test/src/gcc/gcc/tree-ssa-threadbackward.cc:551 0x112f2a73 back_threader::thread_blocks() /home/test/src/gcc/gcc/tree-ssa-threadbackward.cc:975 0x112f2b83 execute /home/test/src/gcc/gcc/tree-ssa-threadbackward.cc:1105 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. compiler exited with status 1 FAIL: 20_util/to_chars/float128_c++23.cc (test for excess errors)
next prev parent reply other threads:[~2023-03-09 15:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-17 21:16 [Bug other/107299] New: [13 regression] seurer at gcc dot gnu.org 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 [this message] 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-zZYm7RJTAz@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).