public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100221] Takes two passes at DSE to remove some dead stores
Date: Tue, 11 Jan 2022 11:04:00 +0000	[thread overview]
Message-ID: <bug-100221-4-REh7WXmyo3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100221-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100221

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Note handling this special case doesn't resolve the issue in the original
testcase since the virtual operand setup is different there.  As said, DSE
is not set up to follow multiple paths to uses (sth akin to maybe_skip_until
for the CSE case), but we only try somewhat hard to reduce multiple paths
to one.

  parent reply	other threads:[~2022-01-11 11:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 20:07 [Bug tree-optimization/100221] New: missed optimization for dead code elimination at -O3 (vs. -O1, -Os, -O2) zhendong.su at inf dot ethz.ch
2021-09-25 10:54 ` [Bug tree-optimization/100221] " pinskia at gcc dot gnu.org
2021-12-16  4:35 ` pinskia at gcc dot gnu.org
2021-12-16  4:50 ` [Bug tree-optimization/100221] Takes two passes at DSE to remove some dead stores pinskia at gcc dot gnu.org
2021-12-16  4:50 ` pinskia at gcc dot gnu.org
2022-01-11 10:16 ` rguenth at gcc dot gnu.org
2022-01-11 11:04 ` rguenth at gcc dot gnu.org [this message]
2022-01-11 11:04 ` rguenth at gcc dot gnu.org
2022-01-11 11:05 ` rguenth at gcc dot gnu.org
2022-05-24  6:20 ` cvs-commit at gcc dot gnu.org
2022-05-24  6:21 ` 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-100221-4-REh7WXmyo3@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: link
Be 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).