From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr, kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [cocci] [RFC] Sharing data processing resources for selected SmPL scripts?
Date: Fri, 5 Sep 2025 11:15:55 +0200 [thread overview]
Message-ID: <ba6b7f45-6c59-4ad1-9b4b-a02f34036d7e@web.de> (raw)
Hello,
I became curious if further developers would like to try the following script out
for the semantic patch language.
@display@
identifier action;
type t;
@@
*t * action(...)
{
... when any
}
I interpret such a search approach in the way that it should extract some data
from a lot of source code places.
Thus I imagine that it results also in special software run time characteristics
which matter especially for big codebases like Linux.
How do you think about to clarify corresponding data collections
and computation resources?
Related source code analysis concerns can eventually be also clarified.
* Handling of function declarations in header files
* Relevance of some preprocessor directives
Regards,
Markus
next reply other threads:[~2025-09-05 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 9:15 Markus Elfring [this message]
2025-09-05 9:42 ` [cocci] [RFC] Sharing data processing resources for selected SmPL scripts? Julia Lawall
2025-09-05 11:14 ` Markus Elfring
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=ba6b7f45-6c59-4ad1-9b4b-a02f34036d7e@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).