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 08:00:17 +0000	[thread overview]
Message-ID: <bug-112450-4-CCLcPEAg2E@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
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org
             Target|                            |riscv

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to JuzheZhong from comment #1)
> Oh. I see we have cond_xxx pattern for VLS modes.
> 
> like V64HImdoe. But we don't support partial vectorization for VLS modes.
> 
> VLS modes are supposed to used as SIMD GNU vectorization.
> 
> As long as COND_XXX is enabled, loop vectorizer considers target support
> partial
> vectorization with mask and since no while_ult, then go through AVX512
> partial vectorization.

I think the bug is in the AVX512 code where it probably lacks some guards.
But in theory even with RVV you can do mask based vectorization of
partial loops, the AVX512 code doesn't require .WHILE_ULT but instead
uses regular compares.

I don't think you should work around this by disabling RVV patterns here.

I can have a look later what happens.

> It seems that for conditional operations, I should use backend RTL PASS to
> walk around that.

  parent reply	other threads:[~2023-11-09  8:00 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 [this message]
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-CCLcPEAg2E@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: link
Be 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).