public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: mstefani@redhat.com (Michael Stefaniuc)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Prepending '*' to an expression (Was: [PATCH V2] scripts/coccinelle/misc/memcpy-assign.cocci: Replace memcpy with struct assignment)
Date: Wed, 06 Feb 2013 15:37:59 +0100	[thread overview]
Message-ID: <51126AC7.70605@redhat.com> (raw)
In-Reply-To: <5108415F.1020603@redhat.com>

On 01/29/2013 10:38 PM, Michael Stefaniuc wrote:
> On 01/28/2013 11:04 PM, Julia Lawall wrote:
>> On Sun, 27 Jan 2013, Michael Stefaniuc wrote:
>>> On 01/26/2013 02:28 AM, Peter Senna Tschudin wrote:
>>>> Thank you for testing.
>>>>
>>>> I made changes on the semantic patch. I believe it fixed the problem.
>>>> Can you test it?
>>> while it does fix the issue it makes the cocci script less readable and
>>> works only in that particular case. Not sure it is worth the effort as
>>> the bad generated patch can be trivially detected and easily fixed
>>> manually. My email was more of a bug report / feature request for
>>> coccinelle than an improvement request to the script.
>>>
>>> Though I've noticed an other issue with the script: Any reason you use
>>> "Options: --no-includes"? While it does speed up things it misses quite
>>> a few cases as a lot of types are defined in the headers.
>>
>> I think it should be --all-includes or even --recursive-includes
> no clue what the policy in the Kernel is but --recursive-includes is
> quite heavy handed as a default. I have one --recursive-includes still
> running for Wine and it accumulated until now over 1126 CPU minutes
The --recursive-includes run finally finished after accumulating 4240
minutes of CPU time. There was no visible slowdown nor memory leak
during the run which is pretty cool.

> (Intel i5 mobile CPU with 2.4 GHz). It found 5 more cases while
> --no-includes found 11 and --local-includes additional 32. The
> --local-includes finished in less than 30 minutes (didn't time it exactly).

bye
	michael

  parent reply	other threads:[~2013-02-06 14:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 22:06 [Cocci] [PATCH V2] scripts/coccinelle/misc/memcpy-assign.cocci: Replace memcpy with struct assignment Peter Senna Tschudin
2013-01-24 17:47 ` [Cocci] Prepending '*' to an expression (Was: [PATCH V2] scripts/coccinelle/misc/memcpy-assign.cocci: Replace memcpy with struct assignment) Michael Stefaniuc
2013-01-24 18:05   ` Julia Lawall
2013-01-26  1:28   ` Peter Senna Tschudin
2013-01-27 20:46     ` Michael Stefaniuc
2013-01-28 22:04       ` Julia Lawall
2013-01-29 21:38         ` Michael Stefaniuc
2013-01-29 21:42           ` Julia Lawall
2013-02-06 14:37           ` Michael Stefaniuc [this message]
2013-02-22 10:25 ` [Cocci] [PATCH V2] scripts/coccinelle/misc/memcpy-assign.cocci: Replace memcpy with struct assignment Michal Marek

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=51126AC7.70605@redhat.com \
    --to=mstefani@redhat.com \
    --cc=cocci@systeme.lip6.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