From: Julia Lawall <julia.lawall@lip6.fr>
To: Timur Tabi <timur@kernel.org>
Cc: cocci <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Can the current function name be passed to a Python snippet?
Date: Wed, 5 Dec 2018 20:33:56 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1812052032520.2971@hadrien> (raw)
In-Reply-To: <CAOZdJXU1k7y3PVqTeXfeSLSbhPuzsbPOUFYh-akVHFifMcOs=w@mail.gmail.com>
On Wed, 5 Dec 2018, Timur Tabi wrote:
> On Wed, Dec 5, 2018 at 12:47 AM Julia Lawall <julia.lawall@lip6.fr> wrote:
> >
> > > and now it works. I don't know why I needed the +'s, but at least it
> > > works now. Thanks.
> >
> > This means that the rule only applies when there is at least one
> > occurrence of the pattern in between the <+... ...+>.
>
> Unfortunately, on some files, adding the + significantly slows down
> the script. It stalls for about 15-20 seconds a few times during
> parsing. Normally the while script takes about 1-2 seconds to run. I
> believe coccinelle is having trouble finding the functions because
> some my source files abuse C macros.
That wouldn't change by using <+... ...+>
Could you send the rule again? I could make another suggestion.
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2018-12-05 19:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 20:58 [Cocci] Can the current function name be passed to a Python snippet? Timur Tabi
2018-11-15 21:29 ` Julia Lawall
2018-12-04 20:17 ` Timur Tabi
2018-12-04 20:25 ` Julia Lawall
2018-12-04 22:02 ` Timur Tabi
2018-12-04 22:19 ` Timur Tabi
2018-12-05 6:35 ` Julia Lawall
2018-12-05 17:49 ` Timur Tabi
2018-12-05 19:33 ` Julia Lawall [this message]
2018-12-05 6:34 ` Julia Lawall
2018-12-05 17:57 ` Timur Tabi
2018-12-05 18:32 ` Timur Tabi
2018-12-05 19:45 ` Julia Lawall
2018-12-05 19:11 ` Timur Tabi
2018-12-05 23:27 ` Timur Tabi
2018-12-06 6:33 ` Julia Lawall
2018-12-05 19:32 ` 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=alpine.DEB.2.21.1812052032520.2971@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=timur@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;
as well as URLs for NNTP newsgroup(s).