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/111765] New: RISC-V: Faild to vectorize gen-vect-34.c Date: Tue, 10 Oct 2023 22:38:40 +0000 [thread overview] Message-ID: <bug-111765-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111765 Bug ID: 111765 Summary: RISC-V: Faild to vectorize gen-vect-34.c 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: --- https://godbolt.org/z/17qYYKWPM float summul(int n, float *arg1, float *arg2) { int i; float res1 = 1.0; for(i = 0; i < n; i++) { if(arg2[i]) res1 *= arg1[i]; } return res1; } I found both ARM SVE and RVV failed to vectorize this case wheras X86 can vectorize it with -mavx2. It seems that we need some tricks on both SVE and RVV backend ?
next reply other threads:[~2023-10-10 22:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-10 22:38 juzhe.zhong at rivai dot ai [this message] 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 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@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).