All of lore.kernel.org
 help / color / mirror / Atom feed
From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Coccinelle: add atomic_as_refcounter script
Date: Tue, 15 Aug 2017 13:02:04 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1708151259550.3849@hadrien> (raw)
In-Reply-To: <f170ecf7-0c9a-c43f-23c0-0e89f928c50e@users.sourceforge.net>



On Tue, 15 Aug 2017, SF Markus Elfring wrote:

> Dear Elena,
>
> Would you like to take another look at my development suggestion for your approach?
> https://systeme.lip6.fr/pipermail/cocci/2017-August/004300.html
>
> How do you think about to refactor another rule like the following?
>
> @r3 exists@
> expression E;
> identifier I=~"^atomic(?:64|_long)?_add_return$";
> position P;
> @@
>  E = I at P(-1, ...);
>
>
> Can the specification of SmPL constraints be occasionally be more succinct
> with the use of regular expressions?

Elena, please don't follow Markus's suggestion.  Coccinelle doesn't
interpret regular expressions when selecting code to work on, and thus the
resulting rule will be less efficient.

Markus, if you see this somehow, at least yesterday all mail sent to you
was bouncing.

julia

  reply	other threads:[~2017-08-15 11:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14  5:59 [PATCH v2] coccinelle: provide rule for finding refcounters Elena Reshetova
2017-08-14  5:59 ` [Cocci] " Elena Reshetova
2017-08-14  5:59 ` [PATCH] Coccinelle: add atomic_as_refcounter script Elena Reshetova
2017-08-14  5:59   ` [Cocci] " Elena Reshetova
2017-08-14 14:16   ` Julia Lawall
2017-08-14 14:16     ` [Cocci] " Julia Lawall
2017-08-15 12:19     ` Reshetova, Elena
2017-08-15 12:19       ` [Cocci] " Reshetova, Elena
2017-08-15 10:55   ` [Cocci] " SF Markus Elfring
2017-08-15 11:02     ` Julia Lawall [this message]
2017-08-15 16:43       ` SF Markus Elfring
2017-08-16 11:52 [PATCH] " Elena Reshetova
2017-08-16 17:00 ` [Cocci] " SF Markus Elfring
2017-08-17  7:22   ` Reshetova, Elena
2017-08-17 11:31     ` SF 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=alpine.DEB.2.20.1708151259550.3849@hadrien \
    --to=julia.lawall@lip6.fr \
    --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.