From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr, kernel-janitors@vger.kernel.org,
linux-hardening@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [RFC] Referencing local variables with SmPL?
Date: Mon, 21 Sep 2026 08:38:43 +0200 [thread overview]
Message-ID: <0562677e-2811-4ccb-bcd5-b00583724612@web.de> (raw)
Hello,
Declarations (and definitions) of local variables tend to be required
for various control flows.
https://en.cppreference.com/c/language/declarations
Function implementations can occasionally use multiple variables with different scopes.
https://github.com/coccinelle/coccinelle/issues/322
Thus it seems to be challenging to refer to relevant data specifications
in a consistent way for source code search and transformation approaches also
by the means of the semantic patch language.
How will corresponding development ideas evolve?
Regards,
Markus
reply other threads:[~2026-09-21 6:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0562677e-2811-4ccb-bcd5-b00583724612@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-hardening@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
all inboxes | Powered by JetHome®