public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104530] [12 Regression] Dead Code Elimination Regression at -O3 (trunk vs. 11.2.0)
Date: Mon, 21 Feb 2022 13:10:52 +0000	[thread overview]
Message-ID: <bug-104530-4-2JT9WxkuM6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104530-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
What could be done in passes like evrp or vrp* but not in unrelated other
passes that use the range infrastructure would be to set uids on stmts
depending on presence of calls that might not always return in the middle of
basic blocks (and perhaps other stmts, wonder about e.g. inline asm),
and optimize whenever the comparison and dereference have the same uid (aka
there is nothing in between that would make the optimization problematic).

  parent reply	other threads:[~2022-02-21 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 16:40 [Bug tree-optimization/104530] New: " theodort at inf dot ethz.ch
2022-02-14 16:47 ` [Bug tree-optimization/104530] " jakub at gcc dot gnu.org
2022-02-15 23:14 ` amacleod at redhat dot com
2022-02-21 13:10 ` jakub at gcc dot gnu.org [this message]
2022-04-19 15:36 ` rguenth at gcc dot gnu.org
2022-05-06  8:32 ` [Bug tree-optimization/104530] [12/13 " jakub at gcc dot gnu.org
2022-11-08  0:22 ` cvs-commit at gcc dot gnu.org
2022-11-08  0:23 ` 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-104530-4-2JT9WxkuM6@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).