public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "juzhe.zhong at rivai dot ai" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/112450] New: RVV vectorization ICE in vect_get_loop_mask, at tree-vect-loop.cc:11037 Date: Thu, 09 Nov 2023 01:14:27 +0000 [thread overview] Message-ID: <bug-112450-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112450 Bug ID: 112450 Summary: RVV vectorization ICE in vect_get_loop_mask, at tree-vect-loop.cc:11037 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: juzhe.zhong at rivai dot ai Target Milestone: --- int a, b, d, e; short c; void f() { for (; e; e++) { int g = 6; for (; g > 2; g--) { int i = -8; while (i < 20) { i += 5; a += b; } c *= d; } b--; } } -O2 --param=riscv-autovec-lmul=m8 -fno-vect-cost-model during GIMPLE pass: vect <source>: In function 'f': <source>:3:6: internal compiler error: in vect_get_loop_mask, at tree-vect-loop.cc:11037 3 | void f() { | ^ 0x7fa31fe47082 __libc_start_main ???:0 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 returned: 1 https://gcc.godbolt.org/z/sda87oaW5 The ICE looks pretty odd. For partial vectorization with length, we should never reach 'vect_get_loop_mask' which is supposed by used by partial vectorization with mask. And it also reaches condition: LOOP_VINFO_PARTIAL_VECTORS_STYLE (loop_vinfo) == vect_partial_vectors_avx512 which should be unlikely for RVV.
next reply other threads:[~2023-11-09 1:14 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-09 1:14 juzhe.zhong at rivai dot ai [this message] 2023-11-09 3:04 ` [Bug tree-optimization/112450] " juzhe.zhong at rivai dot ai 2023-11-09 3:15 ` juzhe.zhong at rivai dot ai 2023-11-09 7:53 ` juzhe.zhong at rivai dot ai 2023-11-09 8:00 ` rguenth at gcc dot gnu.org 2023-11-09 8:10 ` juzhe.zhong at rivai dot ai 2023-11-09 9:55 ` rguenth at gcc dot gnu.org 2023-11-09 10:03 ` juzhe.zhong at rivai dot ai 2023-11-09 10:10 ` juzhe.zhong at rivai dot ai 2023-11-09 10:49 ` rguenth at gcc dot gnu.org 2023-11-09 11:37 ` rguenth at gcc dot gnu.org 2023-11-09 12:32 ` cvs-commit at gcc dot gnu.org 2023-11-12 21:15 ` pinskia 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-112450-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).