public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/112450] RVV vectorization ICE in vect_get_loop_mask, at tree-vect-loop.cc:11037 Date: Thu, 09 Nov 2023 11:37:42 +0000 [thread overview] Message-ID: <bug-112450-4-lPhgWFOZHg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112450-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112450 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|ASSIGNED |RESOLVED --- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> --- commit 8863a7990e9f0cd49c8900605a2c75a0e8886e85 (origin/master, origin/HEAD) Author: Richard Biener <rguenther@suse.de> Date: Thu Nov 9 11:44:07 2023 +0100 tree-optimization/112450 - avoid AVX512 style masking for BImode masks The following avoids running into the AVX512 style masking code for RVV which would theoretically be able to handle it if I were not relying on integer mode maskness in vect_get_loop_mask. While that's easy to fix (patch in PR), the preference is to not have AVX512 style masking for RVV, thus the following. * tree-vect-loop.cc (vect_verify_full_masking_avx512): Check we have integer mode masks as required by vect_get_loop_mask.
next prev parent reply other threads:[~2023-11-09 11:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-09 1:14 [Bug c/112450] New: " juzhe.zhong at rivai dot ai 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 [this message] 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-lPhgWFOZHg@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).