public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Subject: Re: [cocci] [RFC] Increasing usage of direct pointer assignments from memcpy() calls with SmPL?
Date: Fri, 31 Oct 2025 17:57:24 +0100	[thread overview]
Message-ID: <eaaa23b4-a284-46d9-a22c-6ec2a8ca94af@web.de> (raw)
In-Reply-To: <e54a6e57-6bde-f489-f06f-fed9537688df@inria.fr>

> If you have a concern, you have to say what it is.

The initial search pattern might be too simple so far.
Thus I became interested in further software extensions also according to
the discussed source code transformation approach.
Can it be determined anyhow (by the means of the semantic patch language)
that the variable from the assignment statement would not be used any more
after the adjustment within the affected scope?

Regards,
Markus


      parent reply	other threads:[~2025-10-31 16:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 19:56 [cocci] [RFC] Increasing usage of direct pointer assignments from memcpy() calls with SmPL? Markus Elfring
2025-10-29 21:24 ` Julia Lawall
2025-10-30  9:33   ` Markus Elfring
2025-10-30 10:12     ` Julia Lawall
2025-10-30 10:19       ` Markus Elfring
2025-10-30 10:32         ` Julia Lawall
2025-10-30 12:26   ` Markus Elfring
2025-10-30 12:31     ` Julia Lawall
2025-10-30 13:35       ` Markus Elfring
2025-10-30 13:38         ` Julia Lawall
2025-10-30 13:47       ` Dan Carpenter
2025-10-30 13:58         ` Markus Elfring
2025-10-31  6:00         ` Markus Elfring
2025-10-30 14:06   ` Markus Elfring
2025-10-30 14:14     ` Julia Lawall
2025-10-30 14:22       ` Markus Elfring
2025-10-31 16:57   ` 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=eaaa23b4-a284-46d9-a22c-6ec2a8ca94af@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=julia.lawall@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox