public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2015] rs6000: Remove stale rs6000_global_entry_point_needed_p
Date: Thu, 11 Aug 2022 05:38:38 +0000 (GMT)	[thread overview]
Message-ID: <20220811053838.998EE3857BB5@sourceware.org> (raw)

https://gcc.gnu.org/g:7a0e252080e4175a7d6e408ea2aa7a017bb99cce

commit r13-2015-g7a0e252080e4175a7d6e408ea2aa7a017bb99cce
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Aug 10 03:50:17 2022 -0500

    rs6000: Remove stale rs6000_global_entry_point_needed_p
    
    r10-631 had renamed rs6000_global_entry_point_needed_p to
    rs6000_global_entry_point_prologue_needed_p.  This is to
    remove the stale function declaration.
    
    gcc/ChangeLog:
    
            * config/rs6000/rs6000-internal.h (rs6000_global_entry_point_needed_p):
            Remove function declaration.

Diff:
---
 gcc/config/rs6000/rs6000-internal.h | 1 -
 1 file changed, 1 deletion(-)

diff --git a/gcc/config/rs6000/rs6000-internal.h b/gcc/config/rs6000/rs6000-internal.h
index 8ee8c987b81..b9e82c0468d 100644
--- a/gcc/config/rs6000/rs6000-internal.h
+++ b/gcc/config/rs6000/rs6000-internal.h
@@ -82,7 +82,6 @@ extern const char *rs6000_machine;
    from rs6000-logue.cc  */
 
 extern int uses_TOC (void);
-extern bool rs6000_global_entry_point_needed_p (void);
 extern void rs6000_output_function_prologue (FILE *file);
 extern void rs6000_output_function_epilogue (FILE *file);
 extern bool rs6000_function_ok_for_sibcall (tree decl, tree exp);


                 reply	other threads:[~2022-08-11  5:38 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=20220811053838.998EE3857BB5@sourceware.org \
    --to=linkw@gcc.gnu.org \
    --cc=gcc-cvs@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).