public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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: Mon, 27 Sep 2021 07:06:57 +0000 [thread overview]
Message-ID: <bug-100112-4-MPuYwiATPH@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 #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> I _think_ we have an almost exact duplicate but let me take it, this is
> related to last_vuse - we're doing the lookup w/ VN_NOWALK and thus don't
> see the hashtable entry with the "optimized" VUSE from last_vuse handling.
Yes, You are thinking of PR 93891 which I linked here already in the see also
field.
next prev parent reply other threads:[~2021-09-27 7:06 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 [this message]
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
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-MPuYwiATPH@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).