All of lore.kernel.org
 help / color / mirror / Atom feed
From: michelemartone@users.sourceforge.net (Michele Martone)
To: cocci@systeme.lip6.fr
Subject: [Cocci] coccinelle computes patch very slowly
Date: Tue, 26 Jun 2018 12:32:00 +0200	[thread overview]
Message-ID: <20180626103200.GE14796@localhost> (raw)
In-Reply-To: <20180626102638.GD14796@localhost>

On 20180626 at 11:20, SF Markus Elfring wrote:
> > While patching source files of a few thousand lines long,
> > I noticed prohibitively long patch compute times (seemed hanged).
> 
> Do you get nicer run time characteristics if you would refactor the SmPL script
> example like the following for the addition of a type cast?
> 
> // A semantic patch introducing casting on function return:
> @@
> identifier F, V;
> type T;
> @@
>  T V;
>  ...
>  V =
> +    (T)
>      F(...);

Hi Markus,

using your patch
(having F as any identifier, rather than a specific token)
does not change anything time-wise, unfortunately :-(

p.s.: My general problem actually was more complicated than this,
  in that the variables declarations can be anywhere, while this
  patch here requires declaration and F call to be in the same
  scope.

Michele

  parent reply	other threads:[~2018-06-26 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25 15:44 [Cocci] coccinelle computes patch very slowly Michele Martone
     [not found] ` <ff255650-b3d6-c1dc-53ef-8e6e715c5077@users.sourceforge.net>
     [not found]   ` <20180626102638.GD14796@localhost>
2018-06-26 10:32     ` Michele Martone [this message]
2018-06-26 10:56       ` Julia Lawall
2018-06-26 11:03 ` Julia Lawall
2018-06-26 15:27   ` Michele Martone
2018-06-26 15:40     ` Julia Lawall
2018-06-27 22:23       ` Michele Martone
2018-06-27 22:52         ` Julia Lawall

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=20180626103200.GE14796@localhost \
    --to=michelemartone@users.sourceforge.net \
    --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 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.