From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>,
Denis Efremov <efremov@linux.com>,
Coccinelle <cocci@systeme.lip6.fr>
Cc: Michal Marek <michal.lkml@markovi.net>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Cocci] Coccinelle: Improving software components around usage of SmPL disjunctions
Date: Sun, 7 Jun 2020 08:42:42 +0200 [thread overview]
Message-ID: <e06c858b-80fe-9d7c-be48-882162a414fe@web.de> (raw)
In-Reply-To: <bf698c44-4384-e471-3ff0-e38587140b98@web.de>
>> 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
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
prev parent reply other threads:[~2020-06-07 6:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 7:30 [Cocci] [PATCH] coccinelle: api: add kvfree script Markus Elfring
2020-06-06 7:46 ` Julia Lawall
2020-06-06 9:50 ` [Cocci] " Markus Elfring
2020-06-07 14:02 ` [Cocci] Coccinelle: Extending capabilities for source file pre-selection Markus Elfring
2020-06-06 11:06 ` [Cocci] coccinelle: api: add kvfree script Markus Elfring
2020-06-06 11:11 ` Julia Lawall
2020-06-06 11:21 ` Markus Elfring
2020-06-07 6:42 ` Markus Elfring [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=e06c858b-80fe-9d7c-be48-882162a414fe@web.de \
--to=markus.elfring@web.de \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=efremov@linux.com \
--cc=julia.lawall@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
/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).