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/103221] evrp removes |SIGN but does not propagate the ssa name
Date: Wed, 12 Jan 2022 20:52:27 +0000 [thread overview]
Message-ID: <bug-103221-4-eg1Fbzjj6Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103221-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103221
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |WONTFIX
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This bug was asking explictly for evpr to do that. So closing as won't fix
then.
The reasoning why I filed this bug is because between evrp and phiopt1 there is
not a copy prop pass. The next copy prop pass is not until after inlining so
we might not inline as much either. So either we need to reorder some passes
around or add a copy prop pass sooner.
next prev parent reply other threads:[~2022-01-12 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-13 6:54 [Bug tree-optimization/103221] New: " pinskia at gcc dot gnu.org
2021-11-15 9:01 ` [Bug tree-optimization/103221] " rguenth at gcc dot gnu.org
2021-11-23 20:20 ` amacleod at redhat dot com
2021-11-25 15:21 ` amacleod at redhat dot com
2021-12-25 9:59 ` pinskia at gcc dot gnu.org
2022-01-12 20:45 ` amacleod at redhat dot com
2022-01-12 20:52 ` pinskia at gcc dot gnu.org [this message]
2022-01-12 20:59 ` amacleod at redhat dot com
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-103221-4-eg1Fbzjj6Q@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).