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/111794] New: RISC-V: Missed SLP optimization due to mask mode precision
Date: Fri, 13 Oct 2023 07:41:56 +0000 [thread overview]
Message-ID: <bug-111794-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111794
Bug ID: 111794
Summary: RISC-V: Missed SLP optimization due to mask mode
precision
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: ---
void
f (int *restrict x, short *restrict y)
{
x[0] = x[0] == 1 & y[0] == 2;
x[1] = x[1] == 1 & y[1] == 2;
x[2] = x[2] == 1 & y[2] == 2;
x[3] = x[3] == 1 & y[3] == 2;
x[4] = x[4] == 1 & y[4] == 2;
x[5] = x[5] == 1 & y[5] == 2;
x[6] = x[6] == 1 & y[6] == 2;
x[7] = x[7] == 1 & y[7] == 2;
}
Realize that we failed to vectorize this case:
https://godbolt.org/z/rWz9fjM4r
The root cause is the mask bit precision of "small mask mode" (Potentially has
bitsize smaller than 1 bytes).
If we remove this following adjust precision:
ADJUST_PRECISION (V1BI, 1);
ADJUST_PRECISION (V2BI, 2);
ADJUST_PRECISION (V4BI, 4);
ADJUST_PRECISION (RVVMF16BI, riscv_v_adjust_precision (RVVMF16BImode, 4));
ADJUST_PRECISION (RVVMF32BI, riscv_v_adjust_precision (RVVMF32BImode, 2));
ADJUST_PRECISION (RVVMF64BI, riscv_v_adjust_precision (RVVMF64BImode, 1));
It can vectorize such case but will cause bugs in other situations.
Is it possible to fix that in GCC?
next reply other threads:[~2023-10-13 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 7:41 juzhe.zhong at rivai dot ai [this message]
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
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@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).