mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ysato@users.sourceforge.jp
Subject: Re: finding unused header files
Date: Fri, 22 Jun 2012 12:31:45 +0100	[thread overview]
Message-ID: <4FE457A1.2020509@draigBrady.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1206220641150.6493@oneiric>

On 06/22/2012 11:46 AM, Robert P. J. Day wrote:
> 
>   inspired by that last post that located an unused header file under
> arch/h8300, i ran my "find_unused_headers.sh" script on the same
> sub-directory to see what would show up.
> 
>   the script is stupidly conservative and didn't identify that shm.h
> header since *somewhere* in the entire kernel source tree, someone was
> including a file called "shm.h" -- not even for the same architecture.
> like i said, stupidly conservative.
> 
>   but it did find this:
> 
> $ ../s/find_unused_headers.sh arch/h8300
> ===== target_time.h =====
> ./arch/h8300/include/asm/target_time.h
> $
> 
> and i see nothing anywhere in the entire tree that includes a
> target_time.h header under any circumstances.
> 
>   i should probably do another run of these scripts some day, just to
> see what turns up.
> 
> rday
> 

See also:
http://code.google.com/p/include-what-you-use/

It's quite awkward (relies on a llvm/clang source tree for example)
and currently requires human interpretation.

cheers,
Pádraig.

  parent reply	other threads:[~2012-06-22 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 10:46 Robert P. J. Day
2012-06-22 11:03 ` Paul Bolle
2012-06-22 11:31 ` Pádraig Brady [this message]
2012-06-22 11:58 ` Paul Bolle

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=4FE457A1.2020509@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    --cc=ysato@users.sourceforge.jp \
    /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

all inboxes | Powered by JetHome®