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/113583] Main loop in 519.lbm not vectorized. Date: Wed, 24 Jan 2024 15:00:24 +0000 [thread overview] Message-ID: <bug-113583-4-qLWI1Grorb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113583-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113583 --- Comment #3 from JuzheZhong <juzhe.zhong at rivai dot ai> --- Ok I see. If we change NN into 8, then we can vectorize it with load_lanes/store_lanes with group size = 8: https://godbolt.org/z/doe9c3hfo We will use vlseg8e64 which is RVVM1DF[8] == RVVM1x8DFmode. Here there is report: /app/example.c:47:21: missed: no array mode for RVVM1DF[20] /app/example.c:47:21: missed: no array mode for RVVM1DF[20] I believe we enable vec_load_lanes/vec_store_lanes for RVVM1DF[20] which RVVM1x20DF mode, then we can vectorize it. But it's not reasonable and not general way to do that. This code require array size = 20. How about other codes, we may have codes require array size = 21, 22,.. 23, ....etc... The array size can be any number. We can't leverage this approach for infinite array size. So, the idea is that we try to find vec_load_lanes/vec_store_lanes first check whether it support lanes vectorization for specific array size. If not, we should be able to lower them into multiple gather/scatter or strided load/stores.
next prev parent reply other threads:[~2024-01-24 15:00 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-24 14:21 [Bug tree-optimization/113583] New: " rdapp at gcc dot gnu.org 2024-01-24 14:42 ` [Bug tree-optimization/113583] " juzhe.zhong at rivai dot ai 2024-01-24 14:44 ` rdapp at gcc dot gnu.org 2024-01-24 15:00 ` juzhe.zhong at rivai dot ai [this message] 2024-01-25 3:06 ` juzhe.zhong at rivai dot ai 2024-01-25 3:13 ` juzhe.zhong at rivai dot ai 2024-01-25 5:41 ` pinskia at gcc dot gnu.org 2024-01-25 9:05 ` rguenther at suse dot de 2024-01-25 9:16 ` juzhe.zhong at rivai dot ai 2024-01-25 9:34 ` rguenth at gcc dot gnu.org 2024-01-26 9:50 ` rdapp at gcc dot gnu.org 2024-01-26 10:21 ` rguenther at suse dot de 2024-02-05 6:59 ` juzhe.zhong at rivai dot ai 2024-02-07 3:39 ` juzhe.zhong at rivai dot ai 2024-02-07 7:48 ` juzhe.zhong at rivai dot ai 2024-02-07 8:04 ` rguenther at suse dot de 2024-02-07 8:08 ` juzhe.zhong at rivai dot ai 2024-02-07 8:13 ` juzhe.zhong at rivai dot ai 2024-02-07 10:24 ` rguenther at suse dot de 2024-05-13 14:17 ` rdapp at gcc dot gnu.org 2024-05-16 12:41 ` rguenth 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-113583-4-qLWI1Grorb@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).