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/100112] missed optimization for dead code elimination at -O3, -Os (vs. -O1, -O2) Date: Tue, 28 Sep 2021 10:32:00 +0000 [thread overview] Message-ID: <bug-100112-4-xj9Xj81C5G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100112-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100112 --- Comment #10 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:5b8b1522e04adc20980f396571be1929a32d148a commit r12-3918-g5b8b1522e04adc20980f396571be1929a32d148a Author: Richard Biener <rguenther@suse.de> Date: Mon Sep 27 12:01:38 2021 +0200 tree-optimization/100112 - VN last_vuse and redundant store elimination This avoids the last_vuse optimization hindering redundant store elimination by always also recording the original VUSE that was in effect on the load. In stage3 gcc/*.o we have 3182752 times recorded a single entry and 903409 times two entries (that's ~20% overhead). With just recording a single entry the number of hashtable lookups done when walking the vuse->vdef links to find an earlier access is 28961618. When recording the second entry this makes us find that earlier for donwnstream redundant accesses, reducing the number of hashtable lookups to 25401052 (that's a ~10% reduction). 2021-09-27 Richard Biener <rguenther@suse.de> PR tree-optimization/100112 * tree-ssa-sccvn.c (visit_reference_op_load): Record the referece into the hashtable twice in case last_vuse is different from the original vuse on the stmt. * gcc.dg/tree-ssa/ssa-fre-95.c: New testcase.
next prev parent reply other threads:[~2021-09-28 10:32 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 7:22 [Bug tree-optimization/100112] New: " zhendong.su at inf dot ethz.ch 2021-04-20 8:14 ` [Bug ipa/100112] " rguenth at gcc dot gnu.org 2021-09-25 7:51 ` [Bug tree-optimization/100112] " pinskia at gcc dot gnu.org 2021-09-25 9:40 ` pinskia at gcc dot gnu.org 2021-09-27 7:02 ` rguenth at gcc dot gnu.org 2021-09-27 7:06 ` pinskia at gcc dot gnu.org 2021-09-27 7:26 ` rguenth at gcc dot gnu.org 2021-09-27 7:28 ` rguenth at gcc dot gnu.org 2021-09-27 7:28 ` rguenth at gcc dot gnu.org 2021-09-27 7:31 ` rguenth at gcc dot gnu.org 2021-09-28 10:32 ` cvs-commit at gcc dot gnu.org [this message] 2021-09-28 10:32 ` rguenth 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-100112-4-xj9Xj81C5G@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).