From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr, tools@kernel.org
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Determining reachability for selected source code?
Date: Fri, 6 Nov 2026 11:06:07 +0100 [thread overview]
Message-ID: <b0b99c1a-59ff-4948-9e7c-cff3da8acc6e@web.de> (raw)
In-Reply-To: <161f567a-f33-7865-8787-844a299ef9c1@inria.fr>
> I have not tested this. It might not work, or …
Will topics (like the following) become more relevant also for programming interfaces
by the semantic patch language (Coccinelle software)?
* reachability analysis
* dead code elimination
* source code fragment exclusion
* data flow tracking
* call graph
Regards,
Markus
next prev parent reply other threads:[~2026-11-06 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 14:23 [RFC] Replacing special goto statements by direct returns? Markus Elfring
2026-11-03 16:38 ` Julia Lawall
2026-11-03 17:48 ` Markus Elfring
2026-11-04 11:12 ` Markus Elfring
2026-11-06 10:06 ` Markus Elfring [this message]
2026-11-04 12:58 ` Theodore Tso
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=b0b99c1a-59ff-4948-9e7c-cff3da8acc6e@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 \
--cc=tools@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®