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/110897] RISC-V: Fail to vectorize shift Date: Fri, 04 Aug 2023 10:02:35 +0000 [thread overview] Message-ID: <bug-110897-4-BuCm1UA9ga@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110897-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110897 --- Comment #13 from JuzheZhong <juzhe.zhong at rivai dot ai> --- I just checked ARM SVE has the same behavior with RISC-V: https://godbolt.org/z/vY6ecY6Mx You can see this compiler explorer. ARM trunk GCC SVE failed to vectorize it too same as RISCV wheras ARM GCC 13.1 can vectorize it.
next prev parent reply other threads:[~2023-08-04 10:02 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-03 23:18 [Bug c/110897] New: " juzhe.zhong at rivai dot ai 2023-08-03 23:21 ` [Bug target/110897] " pinskia at gcc dot gnu.org 2023-08-03 23:28 ` juzhe.zhong at rivai dot ai 2023-08-04 7:21 ` [Bug tree-optimization/110897] " rguenth at gcc dot gnu.org 2023-08-04 7:24 ` juzhe.zhong at rivai dot ai 2023-08-04 7:40 ` juzhe.zhong at rivai dot ai 2023-08-04 8:50 ` juzhe.zhong at rivai dot ai 2023-08-04 9:16 ` rguenth at gcc dot gnu.org 2023-08-04 9:17 ` rguenth at gcc dot gnu.org 2023-08-04 9:27 ` juzhe.zhong at rivai dot ai 2023-08-04 9:30 ` rsandifo at gcc dot gnu.org 2023-08-04 9:48 ` juzhe.zhong at rivai dot ai 2023-08-04 10:00 ` rsandifo at gcc dot gnu.org 2023-08-04 10:02 ` juzhe.zhong at rivai dot ai [this message] 2023-08-04 10:10 ` juzhe.zhong at rivai dot ai 2023-08-04 11:30 ` rguenth at gcc dot gnu.org 2023-08-04 15:22 ` juzhe.zhong at rivai dot ai 2023-08-06 1:04 ` juzhe.zhong at rivai dot ai 2023-08-06 3:39 ` juzhe.zhong at rivai dot ai 2023-08-07 9:36 ` rguenth at gcc dot gnu.org 2023-08-07 10:21 ` 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-110897-4-BuCm1UA9ga@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).