public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sam at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109304] New: ICE when building Python 3.12.0_alpha6 (internal compiler error: in get_vrange, at value-range-storage.cc:87) Date: Mon, 27 Mar 2023 18:58:18 +0000 [thread overview] Message-ID: <bug-109304-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109304 Bug ID: 109304 Summary: ICE when building Python 3.12.0_alpha6 (internal compiler error: in get_vrange, at value-range-storage.cc:87) Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: sam at gentoo dot org Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Build: x86_64-pc-linux-gnu Created attachment 54771 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54771&action=edit unicodeobject.i.xz Just hit this with this week's gcc 13 (13.0.1 20230326). Last week's was fine. ``` $ x86_64-pc-linux-gnu-gcc -c ./unicodeobject.i -fprofile-generate -O3 -fno-semantic-interposition -fPIC during GIMPLE pass: unswitch Objects/unicodeobject.c: In function ‘_PyUnicode_XStrip’: Objects/unicodeobject.c:11613:1: internal compiler error: in get_vrange, at value-range-storage.cc:87 0x828a6f vrange_storage::get_vrange(void const*, vrange&, tree_node*) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/value-range-storage.cc:87 0x828a6f vrange_storage::get_vrange(void const*, vrange&, tree_node*) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/value-range-storage.cc:72 0x828a6f range_info_get_range(tree_node*, vrange&) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-ssanames.cc:121 0x828a6f duplicate_ssa_name_range_info(tree_node*, tree_node*) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-ssanames.cc:750 0x15ca96a duplicate_ssa_name_fn(function*, tree_node*, gimple*) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-ssanames.cc:771 0x15ca96a duplicate_ssa_name(tree_node*, gimple*) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-ssanames.h:115 0x15ca96a create_new_def_for(tree_node*, gimple*, tree_node**) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-into-ssa.cc:3091 0x15c96cd gimple_duplicate_bb /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-cfg.cc:6555 0x15c8cd5 duplicate_block(basic_block_def*, edge_def*, basic_block_def*, copy_bb_data*) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/cfghooks.cc:1117 0x15c84d2 copy_bbs(basic_block_def**, unsigned int, basic_block_def**, edge_def**, unsigned int, edge_def**, loop*, basic_block_def*, bool) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/cfghooks.cc:1382 0x15fe319 duplicate_loop_body_to_header_edge(loop*, edge_def*, unsigned int, simple_bitmap_def*, edge_def*, vec<edge_def*, va_heap, vl_ptr>*, int) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/cfgloopmanip.cc:1235 0x15fdc4b gimple_duplicate_loop_body_to_header_edge(loop*, edge_def*, unsigned int, simple_bitmap_def*, edge_def*, vec<edge_def*, va_heap, vl_ptr>*, int) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-ssa-loop-manip.cc:861 0x175c533 loop_version(loop*, void*, basic_block_def**, profile_probability, profile_probability, profile_probability, profile_probability, bool) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/cfgloopmanip.cc:1630 0xcf6c7b tree_unswitch_loop /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-ssa-loop-unswitch.cc:1117 0xcf6c7b tree_unswitch_single_loop /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-ssa-loop-unswitch.cc:1055 0xcf85ed tree_ssa_unswitch_loops(function*) /usr/src/debug/sys-devel/gcc-13.0.1_pre20230326/gcc-13-20230326/gcc/tree-ssa-loop-unswitch.cc:385 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. ```
next reply other threads:[~2023-03-27 18:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-27 18:58 sam at gentoo dot org [this message] 2023-03-27 18:59 ` [Bug c/109304] " sam at gentoo dot org 2023-03-27 19:00 ` [Bug tree-optimization/109304] " pinskia at gcc dot gnu.org 2023-03-27 19:00 ` sam at gentoo dot org 2023-03-27 20:22 ` [Bug tree-optimization/109304] [13 Regression] ICE when building Python 3.12.0_alpha6 (internal compiler error: in get_vrange, at value-range-storage.cc:87) since r13-6849-ged626f18b189920a marxin at gcc dot gnu.org 2023-03-27 20:22 ` marxin at gcc dot gnu.org 2023-03-28 7:23 ` [Bug tree-optimization/109304] [13 Regression] ICE in get_vrange, at value-range-storage.cc:87 when building Python 3.12.0_alpha6 " rguenth at gcc dot gnu.org 2023-03-28 7:58 ` rguenth at gcc dot gnu.org 2023-04-04 7:01 ` cvs-commit at gcc dot gnu.org 2023-04-04 7:03 ` marxin 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-109304-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).