All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	Gilles.Muller@lip6.fr, nicolas.palix@imag.fr, mmarek@suse.com,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	gregkh@linuxfoundation.org, markivx@codeaurora.org,
	stephen.boyd@linaro.org, zohar@linux.vnet.ibm.com,
	broonie@kernel.org, ming.lei@canonical.com, tiwai@suse.de,
	johannes@sipsolutions.net, chunkeey@googlemail.com,
	hauke@hauke-m.de, jwboyer@fedoraproject.org,
	dmitry.torokhov@gmail.com, dwmw2@infradead.org, jslaby@suse.com,
	torvalds@linux-foundation.org, cocci@systeme.lip6.fr
Subject: Re: [PATCH v2 4/8] scripts: add glimpse.sh for indexing the kernel
Date: Sat, 18 Jun 2016 12:37:09 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1606181230460.2079@localhost6.localdomain6> (raw)
In-Reply-To: <20160618012243.GD11948@wotan.suse.de>

Overall, idutils seems to be a good choice.  As compared to a grep based 
solution, it knows what is code, so it doesn't report on files where the 
words of interest only occur in comments.  As compared to glimpse, it 
knows that foo_bar is a single word.  Indexing is faster than with 
glimpse, and looking things up in the index is also slightly faster, even 
though Coccinelle needs to make multiple calls because it doesn't support 
complex formulas.  It does support regexps, which could perhaps be even 
faster, but since the running time currently is mostly under 1 second and 
often under .1 seconds, it probably doesn't matter.

julia

WARNING: multiple messages have this Message-ID (diff)
From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [PATCH v2 4/8] scripts: add glimpse.sh for indexing the kernel
Date: Sat, 18 Jun 2016 12:37:09 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1606181230460.2079@localhost6.localdomain6> (raw)
In-Reply-To: <20160618012243.GD11948@wotan.suse.de>

Overall, idutils seems to be a good choice.  As compared to a grep based 
solution, it knows what is code, so it doesn't report on files where the 
words of interest only occur in comments.  As compared to glimpse, it 
knows that foo_bar is a single word.  Indexing is faster than with 
glimpse, and looking things up in the index is also slightly faster, even 
though Coccinelle needs to make multiple calls because it doesn't support 
complex formulas.  It does support regexps, which could perhaps be even 
faster, but since the running time currently is mostly under 1 second and 
often under .1 seconds, it probably doesn't matter.

julia

  parent reply	other threads:[~2016-06-18 10:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 22:31 [PATCH v2 0/8] coccicheck: modernize Luis R. Rodriguez
2016-06-16 22:31 ` [Cocci] " Luis R. Rodriguez
2016-06-16 22:31 ` [PATCH v2 1/8] coccicheck: move spatch binary check up Luis R. Rodriguez
2016-06-16 22:31   ` [Cocci] " Luis R. Rodriguez
2016-06-16 22:31 ` [PATCH v2 2/8] coccicheck: enable parmap support Luis R. Rodriguez
2016-06-16 22:31   ` [Cocci] " Luis R. Rodriguez
2016-06-16 22:31 ` [PATCH v2 3/8] coccicheck: add indexing enhancement options Luis R. Rodriguez
2016-06-16 22:31   ` [Cocci] " Luis R. Rodriguez
2016-06-17  9:47   ` Julia Lawall
2016-06-17  9:47     ` [Cocci] " Julia Lawall
2016-06-17 15:12     ` Luis R. Rodriguez
2016-06-17 15:12       ` [Cocci] " Luis R. Rodriguez
2016-06-17 15:29       ` Julia Lawall
2016-06-17 15:29         ` [Cocci] " Julia Lawall
2016-06-16 22:31 ` [PATCH v2 4/8] scripts: add glimpse.sh for indexing the kernel Luis R. Rodriguez
2016-06-16 22:31   ` [Cocci] " Luis R. Rodriguez
2016-06-17  9:44   ` Julia Lawall
2016-06-17  9:44     ` [Cocci] " Julia Lawall
2016-06-17 15:10     ` Luis R. Rodriguez
2016-06-17 15:10       ` [Cocci] " Luis R. Rodriguez
2016-06-17 15:35       ` Julia Lawall
2016-06-17 15:35         ` [Cocci] " Julia Lawall
2016-06-18  1:22         ` Luis R. Rodriguez
2016-06-18  1:22           ` [Cocci] " Luis R. Rodriguez
2016-06-18  5:51           ` Julia Lawall
2016-06-18  5:51             ` [Cocci] " Julia Lawall
2016-06-20 19:18             ` Luis R. Rodriguez
2016-06-20 19:18               ` [Cocci] " Luis R. Rodriguez
2016-06-18 10:37           ` Julia Lawall [this message]
2016-06-18 10:37             ` Julia Lawall
2016-06-18 10:38             ` Julia Lawall
2016-06-18 10:38               ` [Cocci] " Julia Lawall
2016-06-17 15:18     ` SF Markus Elfring
2016-06-17 15:18       ` SF Markus Elfring
2016-06-17 16:11       ` Julia Lawall
2016-06-17 16:11         ` Julia Lawall
2016-06-16 22:31 ` [PATCH v2 5/8] coccicheck: replace --very-quiet with --quit when debugging Luis R. Rodriguez
2016-06-16 22:31   ` [Cocci] " Luis R. Rodriguez
2016-06-16 22:31 ` [PATCH v2 6/8] coccicheck: add support for requring a coccinelle version Luis R. Rodriguez
2016-06-16 22:31   ` [Cocci] " Luis R. Rodriguez
2016-06-16 22:31 ` [PATCH v2 7/8] coccicheck: refer to coccicheck bottest wiki for documentation Luis R. Rodriguez
2016-06-16 22:31   ` [Cocci] " Luis R. Rodriguez
2016-06-16 22:31 ` [PATCH v2 8/8] scripts/coccinelle: require coccinelle >= 1.0.4 on device_node_continue.cocci Luis R. Rodriguez
2016-06-16 22:31   ` [Cocci] " Luis R. Rodriguez

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.2.02.1606181230460.2079@localhost6.localdomain6 \
    --to=julia.lawall@lip6.fr \
    --cc=Gilles.Muller@lip6.fr \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=chunkeey@googlemail.com \
    --cc=cocci@systeme.lip6.fr \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hauke@hauke-m.de \
    --cc=johannes@sipsolutions.net \
    --cc=jslaby@suse.com \
    --cc=jwboyer@fedoraproject.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markivx@codeaurora.org \
    --cc=mcgrof@kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=mmarek@suse.com \
    --cc=nicolas.palix@imag.fr \
    --cc=stephen.boyd@linaro.org \
    --cc=tiwai@suse.de \
    --cc=torvalds@linux-foundation.org \
    --cc=zohar@linux.vnet.ibm.com \
    /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.