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/97519] builtin_constant_p (x + cst) should be optimized to builtin_constant_p (x)
Date: Thu, 22 Oct 2020 07:02:51 +0000	[thread overview]
Message-ID: <bug-97519-4-01Ks7xRwxz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97519-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Implemented in match.pd it will cover both.  SSA backprop would be the most
natural classical pass candidate but that runs after IPA.  The other candidate
is of course forwprop where it would be "cheaper" (not so many new patterns
to match in match.pd), "chewing" ops during re-processing of processed stmts.

  parent reply	other threads:[~2020-10-22  7:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21 15:14 [Bug tree-optimization/97519] New: " hubicka at gcc dot gnu.org
2020-10-21 16:23 ` [Bug tree-optimization/97519] " pinskia at gcc dot gnu.org
2020-10-21 16:23 ` pinskia at gcc dot gnu.org
2020-10-22  7:02 ` rguenth at gcc dot gnu.org [this message]
2020-10-22  8:23 ` jakub 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-97519-4-01Ks7xRwxz@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).