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/111765] RISC-V: Faild to vectorize gen-vect-34.c
Date: Wed, 11 Oct 2023 02:33:05 +0000 [thread overview]
Message-ID: <bug-111765-4-RRW6Qt3qEp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111765-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111765
--- Comment #2 from JuzheZhong <juzhe.zhong at rivai dot ai> ---
(In reply to Andrew Pinski from comment #1)
> For SVE:
> /app/example.cpp:6:18: missed: missing target support for reduction on
> variable-length vectors.
>
> I assume it is the same issue for RVV.
Yeah.
So may be we should adjust the dump check:
/* { dg-final { scan-tree-dump-times "vectorized 1 loops" 1 "vect" { target
vect_masked_load && !vect_variable_length } } } */
?
next prev parent reply other threads:[~2023-10-11 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 22:38 [Bug c/111765] New: " juzhe.zhong at rivai dot ai
2023-10-11 2:31 ` [Bug tree-optimization/111765] " pinskia at gcc dot gnu.org
2023-10-11 2:33 ` juzhe.zhong at rivai dot ai [this message]
2023-10-11 2:35 ` juzhe.zhong at rivai dot ai
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-111765-4-RRW6Qt3qEp@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).