All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: cocci@inria.fr
Subject: Re: [cocci] Searching for repeated source code with SmPL?
Date: Sat, 11 May 2024 09:15:07 +0200	[thread overview]
Message-ID: <05e493f2-8918-435d-879c-7b317d392fc0@web.de> (raw)
In-Reply-To: <bf850b64-b4bc-4738-9086-43018b8fbe93@web.de>

> Source code parts can occasionally be repeated.
>
> * Loops
>   The control flow can contain ordinary loops.
>
> * Recursion
>   A function may be called by itself.
>
>
> Such constructs trigger special consequences also for further data processing
> with higher level technologies.
>
> + Computation tree logic
>
> + Linear temporal logic
>
>
> I am still looking for clarifications so that the Coccinelle software
> can be applied in safer ways.

Would you like to acknowledge that data processing is influenced also
according to handling of loops and recursion by the means of the provided
technology “computation tree logic with variables and witnesses”?

Do you find a paper like “Cycle Detection in Computation Tree Logic”
interesting for corresponding adjustments?
https://www.fabiomogavero.com/publications/jarticles/2018/fmmps(ic18).pdf
https://dx.doi.org/10.1016/j.ic.2018.09.007

Regards,
Markus

  parent reply	other threads:[~2024-05-11  7:15 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06 10:08 [cocci] Searching for repeated source code with SmPL? Markus Elfring
2024-05-06 10:09 ` Julia Lawall
2024-05-06 11:03   ` Markus Elfring
2024-05-06 12:10   ` Markus Elfring
2024-05-06 12:16     ` Julia Lawall
2024-05-06 12:40       ` Markus Elfring
2024-05-11 15:36   ` Markus Elfring
2024-05-11 16:04     ` Julia Lawall
2024-05-11 16:35       ` Markus Elfring
2024-05-11 16:37         ` Julia Lawall
2024-05-11 17:02           ` Markus Elfring
2024-05-11 17:12             ` Julia Lawall
2024-05-11 17:21               ` Markus Elfring
2024-05-11 17:33                 ` Julia Lawall
2024-05-12  6:48       ` Markus Elfring
2024-05-12  7:34         ` Julia Lawall
2024-05-12  8:01           ` Markus Elfring
2024-05-12  8:10             ` Julia Lawall
2024-05-12  8:33               ` Markus Elfring
2024-05-12  9:17                 ` Julia Lawall
2024-05-12  9:30                   ` Markus Elfring
2024-05-13  9:34                   ` Markus Elfring
2024-05-12 11:24           ` Markus Elfring
2024-05-12 12:53             ` Julia Lawall
2024-05-12 13:07               ` Markus Elfring
2024-05-12 13:13                 ` Julia Lawall
2024-05-12 13:22                   ` Markus Elfring
2024-05-12 14:51                   ` Markus Elfring
2024-05-12 14:57                     ` Julia Lawall
2024-05-11  7:15 ` Markus Elfring [this message]
2024-05-22  8:20 ` Markus Elfring
2024-05-22  8:24   ` Julia Lawall
2024-05-22  8:44     ` Markus Elfring
2024-05-22 13:12     ` Markus Elfring
2024-05-22 15:34       ` Julia Lawall
2024-05-22 16:06         ` 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=05e493f2-8918-435d-879c-7b317d392fc0@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.