[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e06c858b-80fe-9d7c-be48-882162a414fe@web.de>
Date: Sun, 7 Jun 2020 08:42:42 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Julia Lawall <julia.lawall@...ia.fr>,
Denis Efremov <efremov@...ux.com>,
Coccinelle <cocci@...teme.lip6.fr>
Cc: Gilles Muller <Gilles.Muller@...6.fr>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <michal.lkml@...kovi.net>,
Nicolas Palix <nicolas.palix@...g.fr>,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Coccinelle: Improving software components around usage of SmPL
disjunctions
>> But hiding information that could be apparent to the SmPL compiler
>> and could be used to improve the performance of the matching
>> process is not one of them.
>
> Will any software extensions become possible also in this area?
You pointed out that SmPL disjunctions can trigger specific consequences
according to functionality which is different from SmPL constraints.
Both application areas support data processing for function name lists
to some degree.
Each element of a SmPL disjunction refers to a fragment of a detailed
source code search pattern. We are discussing use cases where a search
pattern is occasionally restricted in the way that only identifiers
should be found at a specific place.
* Does this detail provide the opportunity to improve the corresponding
software any more?
* Can a feature request like “Working with variables for case match
identification by SmPL disjunctions” become more interesting?
https://github.com/coccinelle/coccinelle/issues/159
Regards,
Markus
Powered by blists - more mailing lists