Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [obish] -Wunused-function warnings
Date: Thu, 15 Jan 2004 18:46:00 -0000	[thread overview]
Message-ID: <16390.57220.51774.395649@localhost.redhat.com> (raw)
In-Reply-To: <400194E8.10201@gnu.org>

Andrew Cagney writes:
 > Hello,
 > 
 > Attached is a list of all the -Wunused-function warnings that I'm 
 > seeing.  Since all these functions are unreachable (i.e., dead code), I 
 > think their removal is pretty obvious.

 > src/gdb/dwarf2read.c:615: warning: `dwarf2_unsupported_at_frame_base_complaint' defined but not used

yes

 > src/gdb/sh64-tdep.c:835: warning: `sh64_get_gdb_regnum' defined but not used

yes

 > src/gdb/stabsread.c:199: warning: `lrs_general_complaint' defined but not used

yes, leftover from live range splitting cleanup.

 > src/gdb/stabsread.c:540: warning: `ref_search_value' defined but not used

ditto

 > src/gdb/stabsread.c:92: warning: `get_substring' declared `static' but never defined

leftover from cfront cleanup function was deleted but proto is still there.

 > src/gdb/symfile.c:208: warning: `compare_symbols' defined but not used

leftover from David's cleanups.

So all ok.

elena




  parent reply	other threads:[~2004-01-15 18:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 18:26 Andrew Cagney
2004-01-12  2:05 ` Daniel Jacobowitz
2004-01-12 14:58   ` Andrew Cagney
2004-01-15 18:46 ` Elena Zannoni [this message]
2004-01-17  1:04   ` [commit] rm unused symtab & sh functions; Was: " Andrew Cagney
2004-01-19 18:31 ` Andrew Cagney
2004-01-19 23:14   ` Kevin Buettner
2004-01-19 23:21   ` Kevin Buettner
2004-02-03 22:23     ` Andrew Cagney

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=16390.57220.51774.395649@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /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