From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-kbuild@vger.kernel.org, mmarek@suse.cz
Subject: Re: [PATCH] kbuild/tags.sh: use cscope -q option for building symbol db
Date: Thu, 16 Apr 2015 12:48:05 -0700 [thread overview]
Message-ID: <553011F5.6090107@virtuousgeek.org> (raw)
In-Reply-To: <1429213062.16771.90.camel@x220>
On 04/16/2015 12:37 PM, Paul Bolle wrote:
> On Thu, 2015-04-16 at 12:14 -0700, Jesse Barnes wrote:
>> This takes up a bit more disk space, but really improves symbol lookup
>> performance.
>>
>> Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
>> ---
>> scripts/tags.sh | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/scripts/tags.sh b/scripts/tags.sh
>> index cdb491d..bb35d83 100755
>> --- a/scripts/tags.sh
>> +++ b/scripts/tags.sh
>> @@ -142,7 +142,7 @@ all_defconfigs()
>> docscope()
>> {
>> (echo \-k; echo \-q; all_target_sources) > cscope.files
>
> There's an "echo -q" there.
>
>> - cscope -b -f cscope.out
>> + cscope -q -b -f cscope.out
>> }
>>
>> dogtags()
>
> man cscope tells me:
> The -I, -c, -k, -p, -q, and -T options can also be in the cscope.files file
>
> Doesn't the above do that correctly?
I missed that... when I did 'make cscope' after adding the -q option
things must have just gotten faster due to it all being cached, rather
than a change in the db.
Sorry for the noise!
Thanks,
Jesse
prev parent reply other threads:[~2015-04-16 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 19:14 [PATCH] kbuild/tags.sh: use cscope -q option for building symbol db Jesse Barnes
2015-04-16 19:37 ` Paul Bolle
2015-04-16 19:48 ` Jesse Barnes [this message]
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=553011F5.6090107@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.