public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108970] New: [13 Regression] ICE in vect_do_peeling, at tree-vect-loop-manip.cc:2971, or ICE in dump_printf_loc, at dumpfile.cc:1359 Date: Tue, 28 Feb 2023 16:47:17 +0000 [thread overview] Message-ID: <bug-108970-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108970 Bug ID: 108970 Summary: [13 Regression] ICE in vect_do_peeling, at tree-vect-loop-manip.cc:2971, or ICE in dump_printf_loc, at dumpfile.cc:1359 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- 1. gcc 13.0.1 20230226 snapshot (g:e6d39f68d03c46637ca6e1bede3d28eae6278df3) ICEs when compiling the following testcase w/ -O1 -ftree-loop-vectorize -fsave-optimization-record -fno-tree-dce -fno-tree-scev-cprop: int m; __attribute__ ((noinline, returns_twice)) void empty (void) { } void foo (void) { while (m < 1) { empty (); ++m; } } % gcc-13 -O1 -ftree-loop-vectorize -fsave-optimization-record -fno-tree-dce -fno-tree-scev-cprop -c ionf2mqq.c during GIMPLE pass: vect ionf2mqq.c: In function 'foo': ionf2mqq.c:9:1: internal compiler error: in vect_do_peeling, at tree-vect-loop-manip.cc:2971 9 | foo (void) | ^~~ 0x119566f vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**, tree_node**, tree_node**, int, bool, bool, tree_node**) /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vect-loop-manip.cc:2971 0x1187e99 vect_transform_loop(_loop_vec_info*, gimple*) /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vect-loop.cc:10807 0x11c6ca0 vect_transform_loops /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vectorizer.cc:1007 0x11c72de try_vectorize_loop_1 /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vectorizer.cc:1153 0x11c72de try_vectorize_loop /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vectorizer.cc:1183 0x11c7694 execute /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vectorizer.cc:1299 2. Omitting -fsave-optimization-record yields the following instead: % gcc-13 -O1 -ftree-loop-vectorize -fno-tree-dce -fno-tree-scev-cprop -c ionf2mqq.c during GIMPLE pass: vect ionf2mqq.c: In function 'foo': ionf2mqq.c:9:1: internal compiler error: in dump_printf_loc, at dumpfile.cc:1359 9 | foo (void) | ^~~ 0x6c16b2 dump_printf_loc(dump_metadata_t const&, dump_user_location_t const&, char const*, ...) /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/dumpfile.cc:1359 0x119565b vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**, tree_node**, tree_node**, int, bool, bool, tree_node**) /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vect-loop-manip.cc:2969 0x1187e99 vect_transform_loop(_loop_vec_info*, gimple*) /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vect-loop.cc:10807 0x11c6ca0 vect_transform_loops /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vectorizer.cc:1007 0x11c72de try_vectorize_loop_1 /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vectorizer.cc:1153 0x11c72de try_vectorize_loop /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vectorizer.cc:1183 0x11c7694 execute /var/tmp/portage/sys-devel/gcc-13.0.1_p20230226/work/gcc-13-20230226/gcc/tree-vectorizer.cc:1299
next reply other threads:[~2023-02-28 16:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-28 16:47 asolokha at gmx dot com [this message] 2023-02-28 16:50 ` [Bug tree-optimization/108970] " pinskia at gcc dot gnu.org 2023-03-01 7:42 ` rguenth at gcc dot gnu.org 2023-03-01 9:10 ` cvs-commit at gcc dot gnu.org 2023-03-01 9:12 ` 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-108970-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).