[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1606171809150.3164@hadrien>
Date: Fri, 17 Jun 2016 18:11:53 +0200 (CEST)
From: Julia Lawall <julia.lawall@...6.fr>
To: SF Markus Elfring <elfring@...rs.sourceforge.net>
cc: cocci@...teme.lip6.fr, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Christian Lamparter <chunkeey@...glemail.com>,
David Woodhouse <dwmw2@...radead.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Hauke Mehrtens <hauke@...ke-m.de>,
Jiri Slaby <jslaby@...e.com>,
Johannes Berg <johannes@...solutions.net>,
Josh Boyer <jwboyer@...oraproject.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Luis R. Rodriguez" <mcgrof@...nel.org>,
Mark Brown <broonie@...nel.org>,
Michal Marek <mmarek@...e.com>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Ming Lei <ming.lei@...onical.com>,
Stephen Boyd <stephen.boyd@...aro.org>,
Takashi Iwai <tiwai@...e.de>,
Vikram Mulukutla <markivx@...eaurora.org>
Subject: Re: [Cocci] [PATCH v2 4/8] scripts: add glimpse.sh for indexing the
kernel
> Under which circumstances will the indexing efforts pay off?
Indexing is beneficial when a semantic patch uses in an essential way some
words that appear rarely in the code base. For example, the following
semantic patch will only do something useful on code that contains xyz:
- x = kmalloc();
..
- x = xyz();
There is no need to parse the code, match the thousands of occurrences of
kmalloc, nor to do the tracing of execution paths implied by ... if the
code does not contain any call to xyz anyway.
julia
Powered by blists - more mailing lists