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 target/99912] Unnecessary / inefficient spilling of AVX2 ymm registers Date: Thu, 29 Apr 2021 06:32:50 +0000 [thread overview] Message-ID: <bug-99912-4-uFYcRfTewZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99912-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99912 --- 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:b58dc0b803057c0e6032e0d9bd92cd834f72c75c commit r12-248-gb58dc0b803057c0e6032e0d9bd92cd834f72c75c Author: Richard Biener <rguenther@suse.de> Date: Tue Apr 27 14:32:27 2021 +0200 tree-optimization/99912 - delete trivially dead stmts during DSE DSE performs a backwards walk over stmts removing stores but it leaves removing resulting dead SSA defs to later passes. This eats into its own alias walking budget if the removed stores kept loads live. The following patch adds removal of trivially dead SSA defs which helps in this situation and reduces the amount of garbage followup passes need to deal with. 2021-04-28 Richard Biener <rguenther@suse.de> PR tree-optimization/99912 * tree-ssa-dse.c (dse_dom_walker::m_need_cfg_cleanup): New. (dse_dom_walker::todo): Likewise. (dse_dom_walker::dse_optimize_stmt): Move VDEF check to the caller. (dse_dom_walker::before_dom_children): Remove trivially dead SSA defs and schedule CFG cleanup if we removed all PHIs in a block. (pass_dse::execute): Get TODO as computed by the DOM walker and return it. Wipe dominator info earlier. * gcc.dg/pr95580.c: Disable DSE. * gcc.dg/Wrestrict-8.c: Place a use after each memcpy. * c-c++-common/ubsan/overflow-negate-3.c: Make asms volatile to prevent them from being removed. * c-c++-common/ubsan/overflow-sub-4.c: Likewise.
prev parent reply other threads:[~2021-04-29 6:32 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-05 1:53 [Bug target/99912] New: " schnetter at gmail dot com 2021-04-05 1:54 ` [Bug target/99912] " schnetter at gmail dot com 2021-04-05 2:03 ` schnetter at gmail dot com 2021-04-06 8:25 ` rguenth at gcc dot gnu.org 2021-04-06 14:42 ` schnetter at gmail dot com 2021-04-06 16:33 ` schnetter at gmail dot com 2021-04-07 9:36 ` rguenth at gcc dot gnu.org 2021-04-07 16:48 ` rguenth at gcc dot gnu.org 2021-04-27 13:17 ` cvs-commit at gcc dot gnu.org 2021-04-27 13:17 ` cvs-commit at gcc dot gnu.org 2021-04-27 14:02 ` rguenth at gcc dot gnu.org 2021-04-27 16:03 ` schnetter at gmail dot com 2021-04-29 6:32 ` cvs-commit at gcc dot gnu.org [this message]
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-99912-4-uFYcRfTewZ@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).