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/111924] New: Look into using movement_possibility (in tree-ssa-loop-im.cc) for empty_bb_or_one_feeding_into_p for phi-opt
Date: Mon, 23 Oct 2023 00:28:27 +0000	[thread overview]
Message-ID: <bug-111924-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111924
           Summary: Look into using movement_possibility (in
                    tree-ssa-loop-im.cc) for
                    empty_bb_or_one_feeding_into_p for phi-opt
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: internal-improvement
          Severity: enhancement
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

I noticed that movement_possibility/movement_possibility_1 does almost the same
as what some of the checks inside empty_bb_or_one_feeding_into_p does. It seems
like it might be a good idea to combine the 2 into one function and use that in
both PHI-OPT and Loop-im.

Note phi-opt does allow unconditionally a few known builtins/internal functions
too which seems like could benifit IM too.
Oh movement_possibility now disallows some movements of shifts which definitely
could be improved and it is definitely something which PHI-OPT should use too.

             reply	other threads:[~2023-10-23  0:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  0:28 pinskia at gcc dot gnu.org [this message]
2023-10-23  0:29 ` [Bug tree-optimization/111924] " 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-111924-4@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).