mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@inria.fr>, cocci@inria.fr
Cc: LKML <linux-kernel@vger.kernel.org>,
	kernel-janitors@vger.kernel.org,
	Miaoqian Lin <linmq006@gmail.com>
Subject: Re: [cocci] [RFC] Increasing usage of direct pointer assignments from memcpy() calls with SmPL?
Date: Thu, 30 Oct 2025 11:19:10 +0100	[thread overview]
Message-ID: <d227e982-d69d-45b7-9388-9082f86af69c@web.de> (raw)
In-Reply-To: <53e91f9f-bfe5-5c57-157c-fc456bd430ca@inria.fr>

…> I think you would get a more satisfactory result by just removing all of
> the code and adding it back. Then Coccinelle would take charge of laying
> out the whole thing.
…

See also once more:

>> Another SmPL script example might become helpful.
>>
>> @replacement2@
>> expression object, size, source, target;
>> @@
>>  target =
>> -         object; memcpy(target, source, size)
>> +         memcpy(object, source, size)
>>  ;
>>
>>
>> Markus_Elfring@Sonne:…/Projekte/Linux/next-analyses> time /usr/bin/spatch --max-width 100 --no-loops …/Projekte/Coccinelle/janitor/use_memcpy_assignment2.cocci arch/arm64/kvm/arm.c
…>> real    0m0,626s
>> user    0m0,588s
>> sys     0m0,037s


Regards,
Markus

  reply	other threads:[~2025-10-30 10:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 19:56 Markus Elfring
2025-10-29 21:24 ` [cocci] " Julia Lawall
2025-10-30  9:33   ` Markus Elfring
2025-10-30 10:12     ` Julia Lawall
2025-10-30 10:19       ` Markus Elfring [this message]
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

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=d227e982-d69d-45b7-9388-9082f86af69c@web.de \
    --to=markus.elfring@web.de \
    --cc=cocci@inria.fr \
    --cc=julia.lawall@inria.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linmq006@gmail.com \
    --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®