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 tree-optimization/112450] RVV vectorization ICE in vect_get_loop_mask, at tree-vect-loop.cc:11037
Date: Thu, 09 Nov 2023 03:15:38 +0000 [thread overview]
Message-ID: <bug-112450-4-jGu4wtNrjF@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
--- Comment #2 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
if (loop_vinfo
&& LOOP_VINFO_CAN_USE_PARTIAL_VECTORS_P (loop_vinfo)
&& mask_out_inactive)
{
if (cond_len_fn != IFN_LAST
&& direct_internal_fn_supported_p (cond_len_fn, vectype,
OPTIMIZE_FOR_SPEED))
vect_record_loop_len (loop_vinfo, lens, ncopies * vec_num, vectype,
1);
else if (cond_fn != IFN_LAST
&& direct_internal_fn_supported_p (cond_fn, vectype,
OPTIMIZE_FOR_SPEED))
vect_record_loop_mask (loop_vinfo, masks, ncopies * vec_num,
vectype, NULL);
else
{
if (dump_enabled_p ())
dump_printf_loc (MSG_MISSED_OPTIMIZATION, vect_location,
"can't use a fully-masked loop because no"
" conditional operation is available.\n");
LOOP_VINFO_CAN_USE_PARTIAL_VECTORS_P (loop_vinfo) = false;
}
}
go through second condition with
vect_record_loop_mask here.
Seems that we can't differentiate RVV VLS mode with cond_xxx.
RVV VLS mode just want to support COND_XXX to support
for (int i < N)
cond[i]? a[i] + b[i] : c[i]
N is known iterations.
next prev parent reply other threads:[~2023-11-09 3:15 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 [this message]
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-jGu4wtNrjF@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).