public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/104445] New: [12 Regression] ICE in vect_create_partial_epilog, at tree-vect-loop.cc:5098 Date: Tue, 08 Feb 2022 19:39:18 +0000 [thread overview] Message-ID: <bug-104445-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104445 Bug ID: 104445 Summary: [12 Regression] ICE in vect_create_partial_epilog, at tree-vect-loop.cc:5098 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Changed between 20210711 and 20210718, at -O3 or -Ofast : $ cat z1.c signed char a; signed char f (int i, int j) { signed char c; while (i != 0) { a ^= j; ++c; ++i; } return c; } $ gcc-12-20220206 -c z1.c -m32 -O3 -mavx -mno-mmx during GIMPLE pass: vect z1.c: In function 'f': z1.c:2:13: internal compiler error: in vect_create_partial_epilog, at tree-vect-loop.cc:5098 2 | signed char f (int i, int j) | ^ 0xe32e69 vect_create_partial_epilog ../../gcc/tree-vect-loop.cc:5095 0xe3bd5f vect_transform_cycle_phi(_loop_vec_info*, _stmt_vec_info*, gimple**, _slp_tree*, _slp_instance*) ../../gcc/tree-vect-loop.cc:7795 0x190fcad vect_transform_stmt(vec_info*, _stmt_vec_info*, gimple_stmt_iterator*, _slp_tree*, _slp_instance*) ../../gcc/tree-vect-stmts.cc:11276 0xe4b65f vect_transform_loop(_loop_vec_info*, gimple*) ../../gcc/tree-vect-loop.cc:9799 0xe7d565 vect_transform_loops ../../gcc/tree-vectorizer.cc:1004 0xe7d713 vect_transform_loops ../../gcc/tree-vectorizer.cc:1022 0xe7db86 try_vectorize_loop_1 ../../gcc/tree-vectorizer.cc:1133 0xe7db86 try_vectorize_loop ../../gcc/tree-vectorizer.cc:1164 0xe7e0c4 execute ../../gcc/tree-vectorizer.cc:1278
next reply other threads:[~2022-02-08 19:39 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-08 19:39 gscfq@t-online.de [this message] 2022-02-08 20:48 ` [Bug tree-optimization/104445] " pinskia at gcc dot gnu.org 2022-02-09 5:45 ` pinskia at gcc dot gnu.org 2022-02-09 5:48 ` pinskia at gcc dot gnu.org 2022-02-09 7:31 ` rguenth at gcc dot gnu.org 2022-02-09 9:55 ` rguenth at gcc dot gnu.org 2022-02-09 10:01 ` ubizjak at gmail dot com 2022-02-09 10:21 ` rguenth at gcc dot gnu.org 2022-02-09 10:26 ` ubizjak at gmail dot com 2022-02-09 10:48 ` rguenther at suse dot de 2022-02-09 10:59 ` ubizjak at gmail dot com 2022-02-09 11:33 ` rguenth at gcc dot gnu.org 2022-02-09 13:03 ` cvs-commit at gcc dot gnu.org 2022-02-09 13:03 ` 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-104445-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).