public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/111794] RISC-V: Missed SLP optimization due to mask mode precision Date: Fri, 13 Oct 2023 08:13:30 +0000 [thread overview] Message-ID: <bug-111794-4-srg4IYzBiu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111794-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111794 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- I'm failing to see the issue as with -march=rv64gcv I run into t.c:4:8: missed: not vectorized: relevant stmt not supported: *x_50(D) = _6; t.c:4:8: note: removing SLP instance operations starting from: *x_50(D) = _6; t.c:4:8: missed: not vectorized: bad operation in basic block. but just guessing, the issue is bool pattern recognition and t.c:12:1: note: using normal nonmask vectors for _2 = _1 == 1; t.c:12:1: note: using normal nonmask vectors for _4 = _3 == 2; t.c:12:1: note: using normal nonmask vectors for _5 = _2 & _4; ... ? To vectorize you'd want to see t.c:12:1: note: using boolean precision 32 for _2 = _1 == 1; t.c:12:1: note: using boolean precision 16 for _4 = _3 == 2; t.c:12:1: note: using boolean precision 16 for _5 = _2 & _4; ... and a pattern used for the value use: t.c:12:1: note: extra pattern stmt: patt_62 = _5 ? 1 : 0; You need to see why this doesn't work (it's a very delicate area).
next prev parent reply other threads:[~2023-10-13 8:13 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-13 7:41 [Bug c/111794] New: " juzhe.zhong at rivai dot ai 2023-10-13 7:47 ` [Bug c/111794] " juzhe.zhong at rivai dot ai 2023-10-13 7:51 ` juzhe.zhong at rivai dot ai 2023-10-13 8:13 ` rguenth at gcc dot gnu.org [this message] 2023-10-13 8:17 ` rdapp at gcc dot gnu.org 2023-10-16 7:56 ` rdapp at gcc dot gnu.org 2023-10-16 8:50 ` rguenther at suse dot de 2023-10-16 9:05 ` rdapp at gcc dot gnu.org 2023-10-16 9:29 ` rguenther at suse dot de 2023-10-16 9:58 ` rdapp at gcc dot gnu.org 2023-10-16 14:23 ` rdapp at gcc dot gnu.org 2023-10-23 16:44 ` [Bug tree-optimization/111794] " cvs-commit at gcc dot gnu.org 2023-11-01 2:31 ` 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-111794-4-srg4IYzBiu@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).