public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/100089] [11/12 Regression] 30% performance regression for denbench/mp2decoddata2 with -O3 Date: Fri, 21 Jan 2022 13:23:20 +0000 [thread overview] Message-ID: <bug-100089-4-qveb9zASfy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100089-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100089 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:199cd0e0f8744ca1e61a95987b2d020a592a46d9 commit r12-6795-g199cd0e0f8744ca1e61a95987b2d020a592a46d9 Author: Richard Biener <rguenther@suse.de> Date: Fri Jan 21 13:29:06 2022 +0100 tree-optimization/100089 - BB vectorization of if-converted loop bodies The PR complains that when we only partially BB vectorize an if-converted loop body that this can leave unvectorized code unconditionally executed and thus effectively slow down code. For -O2 we already mitigated the issue by not doing BB vectorization when not all if-converted stmts were covered but the issue is present with -O3 as well. Thus the following simply extends the fix to cover all but the unlimited cost models. It is after all very likely that we vectorize some stmts, if only a single paired store. 2022-01-21 Richard Biener <rguenther@suse.de> PR tree-optimization/100089 * tree-vect-slp.cc (vect_slp_region): Reject BB vectorization of if-converted loops with unvectorized COND_EXPRs for all but the unlimited cost models.
next prev parent reply other threads:[~2022-01-21 13:23 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-15 6:35 [Bug tree-optimization/100089] New: [11 Performance regression ] 30% " crazylht at gmail dot com 2021-04-15 7:17 ` [Bug tree-optimization/100089] [11 Regression] 30% performance regression " rguenth at gcc dot gnu.org 2021-04-27 11:40 ` [Bug tree-optimization/100089] [11/12 " jakub at gcc dot gnu.org 2021-05-12 8:19 ` rsandifo at gcc dot gnu.org 2021-05-12 8:27 ` rguenth at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2021-08-23 12:47 ` rguenth at gcc dot gnu.org 2021-08-24 1:28 ` cvs-commit at gcc dot gnu.org 2021-08-24 9:36 ` rguenth at gcc dot gnu.org 2021-08-24 10:34 ` rguenth at gcc dot gnu.org 2021-08-24 12:23 ` cvs-commit at gcc dot gnu.org 2021-08-24 12:27 ` rguenth at gcc dot gnu.org 2021-08-30 12:05 ` rguenth at gcc dot gnu.org 2021-08-31 10:27 ` rguenth at gcc dot gnu.org 2022-01-21 12:34 ` rguenth at gcc dot gnu.org 2022-01-21 13:23 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-21 13:24 ` [Bug tree-optimization/100089] [11 " rguenth at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2023-05-29 10:04 ` jakub 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-100089-4-qveb9zASfy@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).