From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [cocci] [RFC] Sharing data processing resources for selected SmPL scripts?
Date: Fri, 5 Sep 2025 13:14:08 +0200 [thread overview]
Message-ID: <b22df436-7bf1-4909-8150-03b65f657a60@web.de> (raw)
In-Reply-To: <a00a59b-3079-d55c-eaf6-2db4c14f92a3@inria.fr>
>> @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.
>
> I guess it would be quite fast,
I am curious how such development views will evolve further
(depending on the data processing environment you may use).
> because it will just find the deader of
> each function.
Header information should be found for several function implementations
from selected directories.
If you would dare to try the shown SmPL script out on the complete Linux codebase,
a huge diff output will probably be generated.
It might be more helpful to try it out on a few header/source files
with a more reasonable size.
Other data structures might become also more attractive for the storage
and documentation of found pointer types in combination with known functions.
Regards,
Markus
prev parent reply other threads:[~2025-09-05 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 9:15 [cocci] [RFC] Sharing data processing resources for selected SmPL scripts? Markus Elfring
2025-09-05 9:42 ` Julia Lawall
2025-09-05 11:14 ` 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=b22df436-7bf1-4909-8150-03b65f657a60@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=julia.lawall@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).