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/107822] [13/14 Regression] Dead Code Elimination Regression at -Os (trunk vs. 12.2.0)
Date: Fri, 24 Mar 2023 08:28:16 +0000 [thread overview]
Message-ID: <bug-107822-4-lCIoQjXLLj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107822-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107822
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|13.0 |14.0
Summary|[13 Regression] Dead Code |[13/14 Regression] Dead
|Elimination Regression at |Code Elimination Regression
|-Os (trunk vs. 12.2.0) |at -Os (trunk vs. 12.2.0)
Priority|P1 |P2
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
I don't see us realistically fixing this for GCC 13, so postponing to GCC 14
and downgrading from P1 to P2.
Besides bringing back a pass that performs propagation itself possibly using
value-range and range-op helpers it might be possible to teach the on-demand
ranger to process SSA SCCs in the special way the old code did (but
only when asked for?). But teaching ranger about SCCs probably requires
extensive changes in the code doing the global "propagation", and I'm not
sure that's a) desirable or b) even possible in some reasonable manner.
Adding ad-hoc SCC discovery ontop of the existing "propagation" probably
does not make much sense.
next prev parent reply other threads:[~2023-03-24 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 17:51 [Bug tree-optimization/107822] New: " yann at ywg dot ch
2022-11-22 21:21 ` [Bug tree-optimization/107822] [13 Regression] " pinskia at gcc dot gnu.org
2022-12-21 13:48 ` rguenth at gcc dot gnu.org
2023-01-03 17:46 ` amacleod at redhat dot com
2023-02-27 10:15 ` rguenth at gcc dot gnu.org
2023-03-24 8:28 ` rguenth at gcc dot gnu.org [this message]
2023-03-27 20:47 ` [Bug tree-optimization/107822] [13/14 " amacleod at redhat dot com
2023-05-24 21:19 ` [Bug tree-optimization/107822] [13/14/14 " cvs-commit at gcc dot gnu.org
2023-08-09 4:27 ` pinskia 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-107822-4-lCIoQjXLLj@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).