public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-4106] Remove dead code in config/rs6000/vxworks.h
Date: Mon,  4 Oct 2021 07:19:39 +0000 (GMT)	[thread overview]
Message-ID: <20211004071939.41B083858405@sourceware.org> (raw)

https://gcc.gnu.org/g:f950d946370bb7b8751f7b89ff856beddbe91aea

commit r12-4106-gf950d946370bb7b8751f7b89ff856beddbe91aea
Author: Eric Botcazou <ebotcazou@adacore.com>
Date:   Mon Oct 4 09:16:19 2021 +0200

    Remove dead code in config/rs6000/vxworks.h
    
    These lines were added last year:
    
    /* Initialize library function table.  */
     #undef TARGET_INIT_LIBFUNCS
     #define TARGET_INIT_LIBFUNCS rs6000_vxworks_init_libfuncs
    
    but TARGET_INIT_LIBFUNCS is #undef-ed in config/rs6000/rs6000.c and
    rs6000_vxworks_init_libfuncs is nowhere defined in any case.
    
    gcc/
            * config/rs6000/vxworks.h (TARGET_INIT_LIBFUNCS): Delete.

Diff:
---
 gcc/config/rs6000/vxworks.h | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/gcc/config/rs6000/vxworks.h b/gcc/config/rs6000/vxworks.h
index 5facbbb392f..d8ecc0296c8 100644
--- a/gcc/config/rs6000/vxworks.h
+++ b/gcc/config/rs6000/vxworks.h
@@ -147,10 +147,6 @@ along with GCC; see the file COPYING3.  If not see
 #undef FUNCTION_PROFILER
 #define FUNCTION_PROFILER(FILE,LABELNO) VXWORKS_FUNCTION_PROFILER(FILE,LABELNO)
 
-/* Initialize library function table.  */
-#undef TARGET_INIT_LIBFUNCS
-#define TARGET_INIT_LIBFUNCS rs6000_vxworks_init_libfuncs
-
 /* Nor sdata, for kernel mode.  We use this in
    SUBSUBTARGET_INITIALIZE_OPTIONS, after rs6000_rtp has been initialized.  */
 #undef SDATA_DEFAULT_SIZE


                 reply	other threads:[~2021-10-04  7:19 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=20211004071939.41B083858405@sourceware.org \
    --to=ebotcazou@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).