public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tsukasa OI <a4lg@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] sim/sh: Remove redundant function declaration
Date: Sat, 29 Oct 2022 08:15:15 +0000 (GMT)	[thread overview]
Message-ID: <20221029081523.ED6BD385840E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9b77569146a8ec354a6010497049428d2a9ceb1d

commit 9b77569146a8ec354a6010497049428d2a9ceb1d
Author: Tsukasa OI <research_trasio@irq.a4lg.com>
Date:   Sat Sep 24 09:11:52 2022 +0000

    sim/sh: Remove redundant function declaration
    
    Clang generates a warning if there is a function declaration/definition
    with zero arguments.  Such declarations/definitions without a prototype (an
    argument list) are deprecated forms of indefinite arguments
    ("-Wdeprecated-non-prototype").  On the default configuration, it causes a
    build failure (unless "--disable-werror" is specified).
    
    But there is another issue.  This function declaration in sim/sh/interp.c
    is completely redundant.  This commit just removes that declaration.

Diff:
---
 sim/sh/interp.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/sim/sh/interp.c b/sim/sh/interp.c
index 38f3f945a35..b6f29880d74 100644
--- a/sim/sh/interp.c
+++ b/sim/sh/interp.c
@@ -1492,8 +1492,6 @@ get_loop_bounds (int rs, int re, unsigned char *memory, unsigned char *mem_end,
   return loop;
 }
 
-static void ppi_insn ();
-
 #include "ppi.c"
 
 /* Provide calloc / free versions that use an anonymous mmap.  This can

                 reply	other threads:[~2022-10-29  8:15 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=20221029081523.ED6BD385840E@sourceware.org \
    --to=a4lg@sourceware.org \
    --cc=gdb-cvs@sourceware.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).