From: Michal Marek <mmarek@suse.cz>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: tags: include headers before source files
Date: Fri, 05 Feb 2010 22:59:08 +0100 [thread overview]
Message-ID: <4B6C94AC.7000301@suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.1002031704550.6324@axis700.grange>
On 3.2.2010 17:25, Guennadi Liakhovetski wrote:
> Currently looking up a structure definition in TAGS / tags takes one to
> one of multiple "static struct X" definitions in arch sources, which makes
> it for many structs practically impossible to get to the required header.
> This patch changes the order of sources being tagged to first scan
> architecture includes, then the top-level include/ directory, and only
> then the rest. It also takes into account, that many architectures have
> more than one include directory, i.e., not only arch/$ARCH/include, but
> also arch/$ARCH/mach-X/include etc.
Hi Guennadi
This is a cool idea, but there is one issue:
> # find sources in arch/$1/include
> find_arch_include_sources()
> {
> - find ${tree}arch/$1/include $ignore -name "$2" -print;
> + include=$(find ${tree}arch/$1/ -name include -type d);
> + archincludedir+=$include
> + find $include $ignore -name "$2" -print;
You need to check if $include isn't empty, which it is on i386 or x86_64
(and on other archs where $ARCH != $SRCARCH). If I do a 'make cscope'
after your change, the second find statement crawls the whole filesystem.
Michal
next prev parent reply other threads:[~2010-02-05 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 16:25 tags: include headers before source files Guennadi Liakhovetski
2010-02-05 21:59 ` Michal Marek [this message]
2010-02-07 23:25 ` [PATCH v2] " Guennadi Liakhovetski
2010-02-17 13:05 ` Michal Marek
2010-02-07 16:13 ` Américo Wang
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=4B6C94AC.7000301@suse.cz \
--to=mmarek@suse.cz \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).