From: Christopher Li <sparse@chrisli.org>
To: Marko Kreen <markokr@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
sparse <linux-sparse@vger.kernel.org>
Subject: Re: Detect unused header files?
Date: Thu, 6 Aug 2009 10:39:23 -0700 [thread overview]
Message-ID: <70318cbf0908061039r72dfef6kceed5ba879562d0b@mail.gmail.com> (raw)
In-Reply-To: <e51f66da0908060414n62a34b89n322f516878567141@mail.gmail.com>
On Thu, Aug 6, 2009 at 4:14 AM, Marko Kreen<markokr@gmail.com> wrote:
> Could we have a flag to track top-level headers only? So that
> anything declared in sub-headers will be registered also under
> top header file? This seems more useful scanning mode for regular
> user-space code.
Yes, we can. It might not help Sam much though because he is
interested to find out unused header file in system header files.
One way to do it is just let stream keep track of its parent and
is_toplevel.
Just add another pass inside show_unused_streams(). Mark all used
stream's parents as used.
Should be straight forward enough to implement base on branch
"unused-include-files". Any brave sparse hackers want to
give it a try?
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-06 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 18:18 Detect unused header files? Sam Ravnborg
2009-07-28 20:36 ` Christopher Li
2009-07-28 20:36 ` Robert P. J. Day
2009-07-28 20:49 ` Christopher Li
2009-07-28 21:04 ` Sam Ravnborg
2009-07-28 21:38 ` Christopher Li
2009-07-30 10:55 ` Christopher Li
2009-07-30 11:12 ` Derek M Jones
2009-07-30 20:36 ` Sam Ravnborg
2009-08-04 21:49 ` Christopher Li
2009-08-05 6:12 ` Sam Ravnborg
2009-08-06 11:14 ` Marko Kreen
2009-08-06 11:17 ` Robert P. J. Day
2009-08-06 12:16 ` Kamil Dudka
2009-08-06 12:15 ` Robert P. J. Day
2009-08-06 13:01 ` Kamil Dudka
2009-08-06 13:26 ` Michael Stefaniuc
2009-08-06 14:09 ` Robert P. J. Day
2009-08-06 17:39 ` Christopher Li [this message]
2009-07-28 20:58 ` Sam Ravnborg
2009-07-28 21:21 ` Christopher Li
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=70318cbf0908061039r72dfef6kceed5ba879562d0b@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=markokr@gmail.com \
--cc=rpjday@crashcourse.ca \
--cc=sam@ravnborg.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 NNTP newsgroup(s).