public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Cc: kernel-janitors@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [cocci] [RFC] Choosing “semantics” better for SmPL script parts?
Date: Mon, 25 Aug 2025 09:30:24 +0200	[thread overview]
Message-ID: <eb3e0445-39fa-4f4a-aeed-96eadc94657d@web.de> (raw)
In-Reply-To: <574a6fa0-00a0-43c2-8e66-cc6443f5cfd4@web.de>

> A bit of information is provided about special “semantics” (also in the manual
> for the semantic patch language).

The usage of the semantic match functionality influences which default semantics
should be applied for the evaluation of an SmPL rule.
I imagine that the corresponding data processing can become more interesting
when the needed semantics would actually be the opposite setting.

* Do you tend to look for the existence of selected implementation details
  more than that source code variants can occur on all executions paths
  according to evolving control flows?

* Would you expect to use the source code search parameter “exists” more often
  then “forall”?


Regards,
Markus

  reply	other threads:[~2025-08-25  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24 12:40 [cocci] [RFC] Choosing “semantics” better for SmPL script parts? Markus Elfring
2025-08-25  7:30 ` Markus Elfring [this message]
2025-08-25 13:23   ` Julia Lawall
2025-08-25 15:17     ` Markus Elfring
2025-08-26  7:30     ` 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=eb3e0445-39fa-4f4a-aeed-96eadc94657d@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