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/111401] New: Middle-end: Missed optimization of MASK_LEN_FOLD_LEFT_PLUS Date: Wed, 13 Sep 2023 09:31:51 +0000 [thread overview] Message-ID: <bug-111401-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111401 Bug ID: 111401 Summary: Middle-end: Missed optimization of MASK_LEN_FOLD_LEFT_PLUS 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: --- There is a case I think I missed the optimization in the loop vectorizer: https://godbolt.org/z/x5sjdenhM double foo2 (double *__restrict a, double init, int *__restrict cond, int n) { for (int i = 0; i < n; i++) if (cond[i]) init += a[i]; return init; } It generate the GIMPLE IR as follows: _60 = .SELECT_VL (ivtmp_58, 4); ... vect__ifc__35.14_56 = .VCOND_MASK (mask__23.10_50, vect__8.13_54, { 0.0, 0.0, 0.0, 0.0 }); _36 = .MASK_LEN_FOLD_LEFT_PLUS (init_20, vect__ifc__35.14_56, { -1, -1, -1, -1 }, _60, 0); The mask of MASK_LEN_FOLD_LEFT_PLUS is the dummy mask {-1.-1,...-1} I think we should forward the mask of VCOND_MASK into the MASK_LEN_FOLD_LEFT_PLUS. Then we can eliminate the VCOND_MASK. I don't where is the optimal place to do the optimization. Should be the match.pd ? or the loop vectorizer code? Thanks.
next reply other threads:[~2023-09-13 9:31 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-13 9:31 juzhe.zhong at rivai dot ai [this message] 2023-09-13 9:46 ` [Bug c/111401] " rguenth at gcc dot gnu.org 2023-09-13 16:52 ` [Bug middle-end/111401] " rdapp at gcc dot gnu.org 2023-09-13 21:25 ` rdapp at gcc dot gnu.org 2023-09-14 6:46 ` rguenther at suse dot de 2023-09-14 6:51 ` rguenther at suse dot de 2023-09-14 15:07 ` rdapp at gcc dot gnu.org 2023-09-15 6:42 ` rguenth at gcc dot gnu.org 2023-11-02 10:50 ` cvs-commit at gcc dot gnu.org 2023-11-02 22:40 ` 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-111401-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).