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/111594] New: RISC-V: Failed to fold VEC_COND_EXPR and COND_LEN_ADD Date: Tue, 26 Sep 2023 02:31:44 +0000 [thread overview] Message-ID: <bug-111594-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111594 Bug ID: 111594 Summary: RISC-V: Failed to fold VEC_COND_EXPR and COND_LEN_ADD 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: --- Consider this following case: #include <stdint.h> void single_loop_with_if_condition(uint64_t * restrict a, uint64_t * restrict b, int loop_size) { uint64_t result = 0; for (int i = 0; i < loop_size; i++) { if (b[i] <= a[i]) { result += a[i]; } } a[0] = result; } In ARM SVE: vect__ifc__33.15_48 = VEC_COND_EXPR <mask__18.14_46, vect__7.13_45, { 0, ... }>; vect__34.16_49 = .COND_ADD (loop_mask_41, vect_result_19.7_38, vect__ifc__33.15_48, vect_result_19.7_38); will be folded into: vect__34.16_49 = .COND_ADD (_50, vect_result_19.7_38, vect__7.13_45, vect_result_19.7_38); However, for RVV, if failed to fold VEC_COND_EXPR + COND_LEN_ADD. vect__ifc__44.30_96 = VEC_COND_EXPR <mask__43.29_94, vect__42.28_93, { 0, ... }>; vect__45.31_97 = .COND_LEN_ADD ({ -1, ... }, vect_result_35.22_78, vect__ifc__44.30_96, vect_result_35.22_78, _104, 0); I am not sure where to do this optimization?
next reply other threads:[~2023-09-26 2:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-26 2:31 juzhe.zhong at rivai dot ai [this message] 2023-09-26 2:46 ` [Bug middle-end/111594] " pinskia at gcc dot gnu.org 2023-09-26 3:02 ` juzhe.zhong at rivai dot ai 2023-09-26 3:42 ` juzhe.zhong at rivai dot ai 2023-09-26 3:59 ` pinskia at gcc dot gnu.org 2023-09-26 12:20 ` cvs-commit at gcc dot gnu.org 2023-09-26 12:29 ` 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-111594-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).