Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFA/commit] procfs.c: Remove unused functions and make many functions static
Date: Fri, 04 May 2012 09:10:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1205040935240.18334@tp.orcam.me.uk> (raw)
In-Reply-To: <1336000479-30511-1-git-send-email-brobecker@adacore.com>

On Thu, 3 May 2012, Joel Brobecker wrote:

> This is something that was triggered after seeing a patch silencing
> some -Wmissing-prototypes errors in procfs.c.  The diff made me wonder
> about why we had so many non-static functions in procfs.c.  Turns out
> most of them can actually be static.
> 
> This patches the functions that can be static into static functions.
> It removes advances declarations when unnecessary.
> 
> And it also delete unused functions...

 I hesitated doing that in the change you must obviously have in mind 
because it appeared to me that this source file wants to present a 
complete API to /proc services, even if some parts are not actually 
(currently) used by GDB (but may be or may have been sometime).  Hence all 
the unused functions have prototypes and are defined with external linkage 
or GCC (and possibly some other compilers) would have complained about 
them long ago, before -Wmissing-prototypes was added.

 What is unclear to me of course is whether the availability of the 
complete API (if my perception is indeed correct) is relevant any longer 
and why the prototypes have never been moved to a header clients could 
use.  The file is very old:

Thu Oct 24 01:32:51 1991  Fred Fish  (fnf at cygnus.com)

	* procfs.c: New file for SVR4 /proc (process file system) support.

and a corresponding header was not added back then even though it had 
clients (a common practice once, sigh, for any client to use its own 
locally provided prototypes or even rely on default declarations).

  Maciej


  reply	other threads:[~2012-05-04  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 23:15 Joel Brobecker
2012-05-04  9:10 ` Maciej W. Rozycki [this message]
2012-05-04 12:35   ` Joel Brobecker
2012-05-04 22:49     ` Maciej W. Rozycki
2012-05-07  8:24       ` Maciej W. Rozycki
2012-05-17 17:35 ` Joel Brobecker
2012-05-17 19:26   ` Maciej W. Rozycki
2012-05-17 20:43     ` Joel Brobecker

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=alpine.DEB.1.10.1205040935240.18334@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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