public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Make add_phi_node_to_bb static
Date: Wed, 2 Aug 2023 11:51:33 +0000 (UTC)	[thread overview]
Message-ID: <20230802115133.Zo6Il-LOtsbiKxpm1yTcQ30RAHlvtI4SKm6gRTL60KU@z> (raw)

The only exported PHI allocation already adds the PHI node to a block.

Bootstrapped on x86_64-unknown-linux-gnu, pushed.

	* tree-phinodes.h (add_phi_node_to_bb): Remove.
	* tree-phinodes.cc  (add_phi_node_to_bb): Make static.
---
 gcc/tree-phinodes.cc | 3 +--
 gcc/tree-phinodes.h  | 1 -
 2 files changed, 1 insertion(+), 3 deletions(-)

diff --git a/gcc/tree-phinodes.cc b/gcc/tree-phinodes.cc
index 976f3dbae10..63baec4c16a 100644
--- a/gcc/tree-phinodes.cc
+++ b/gcc/tree-phinodes.cc
@@ -315,7 +315,7 @@ reserve_phi_args_for_new_edge (basic_block bb)
 
 /* Adds PHI to BB.  */
 
-void
+static void
 add_phi_node_to_bb (gphi *phi, basic_block bb)
 {
   gimple_seq seq = phi_nodes (bb);
@@ -330,7 +330,6 @@ add_phi_node_to_bb (gphi *phi, basic_block bb)
 
   /* Associate BB to the PHI node.  */
   gimple_set_bb (phi, bb);
-
 }
 
 /* Create a new PHI node for variable VAR at basic block BB.  */
diff --git a/gcc/tree-phinodes.h b/gcc/tree-phinodes.h
index be114e317b4..99209ad3392 100644
--- a/gcc/tree-phinodes.h
+++ b/gcc/tree-phinodes.h
@@ -22,7 +22,6 @@ along with GCC; see the file COPYING3.  If not see
 
 extern void phinodes_print_statistics (void);
 extern void reserve_phi_args_for_new_edge (basic_block);
-extern void add_phi_node_to_bb (gphi *phi, basic_block bb);
 extern gphi *create_phi_node (tree, basic_block);
 extern void add_phi_arg (gphi *, tree, edge, location_t);
 extern void remove_phi_args (edge);
-- 
2.35.3

                 reply	other threads:[~2023-08-02 11:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230802115133.Zo6Il-LOtsbiKxpm1yTcQ30RAHlvtI4SKm6gRTL60KU@z \
    --to=rguenther@suse.de \
    --cc=gcc-patches@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).