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/107009] [13 Regression] massive unnecessary code blowup in vectorizer Date: Mon, 26 Sep 2022 14:42:35 +0000 [thread overview] Message-ID: <bug-107009-4-HZG17MNp03@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107009-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107009 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>: https://gcc.gnu.org/g:2460f7cdef7ef9c971de79271afc0db73687a272 commit r13-2876-g2460f7cdef7ef9c971de79271afc0db73687a272 Author: Aldy Hernandez <aldyh@redhat.com> Date: Fri Sep 23 19:47:33 2022 +0200 Set ranges from unreachable edges for all known ranges. In the conversion of DOM+evrp to DOM+ranger, we missed that evrp was exporting ranges for unreachable edges for all SSA names for which we have ranges for. Instead we have only been exporting ranges for the SSA name in the final conditional to the BB involving the unreachable edge. This patch adjusts adjusts DOM to iterate over the exports, similarly to what evrp was doing. Note that I also noticed that we don't calculate the nonzero bit mask for op1, when 0 = op1 & MASK. This isn't needed for this PR, since maybe_set_nonzero_bits() is chasing the definition and parsing the bitwise and on its own. However, I'll be adding the functionality for completeness sake, plus we could probably drop the maybe_set_nonzero_bits legacy call entirely. PR tree-optimization/107009 gcc/ChangeLog: * tree-ssa-dom.cc (dom_opt_dom_walker::set_global_ranges_from_unreachable_edges): Iterate over exports. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/pr107009.c: New test.
next prev parent reply other threads:[~2022-09-26 14:42 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-22 18:49 [Bug tree-optimization/107009] New: " drepper.fsp+rhbz at gmail dot com 2022-09-22 19:00 ` [Bug tree-optimization/107009] [13 Regression] " mpolacek at gcc dot gnu.org 2022-09-22 20:03 ` aldyh at gcc dot gnu.org 2022-09-23 6:43 ` rguenth at gcc dot gnu.org 2022-09-23 13:57 ` aldyh at gcc dot gnu.org 2022-09-23 17:56 ` aldyh at gcc dot gnu.org 2022-09-23 17:57 ` aldyh at gcc dot gnu.org 2022-09-23 17:57 ` aldyh at gcc dot gnu.org 2022-09-26 14:42 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-26 14:43 ` aldyh at gcc dot gnu.org 2022-09-26 17:25 ` cvs-commit 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-107009-4-HZG17MNp03@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).