From: Julia Lawall <julia.lawall@lip6.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Checking redundant variable initialisations with SmPL?
Date: Sun, 23 Jun 2019 14:55:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1906231454520.4961@hadrien> (raw)
In-Reply-To: <5f436d79-b510-b0a3-d11a-d92b8d175f7f@web.de>
[-- Attachment #1: Type: text/plain, Size: 1976 bytes --]
On Sun, 23 Jun 2019, Markus Elfring wrote:
> > Yu can do whatever you want, but you will get lotsof false positives if
> > you keep it. If you really want a star on the declaration then you need
> > to make two rules. The first that finds the positions of the places that
> > match and the second that only puts a * when there is both a matched
> > declaration and a matched reinitialization.
>
> I hoped that the following SmPL script variant can be another approximation
> for the desired solution on the discussed source code search pattern.
>
>
> @display@
> binary operator bo1, bo2;
> expression action, e1, e2 != e1, e3, e4, e5;
> identifier var;
> statement es1, is2, es2, is3, es3;
> type t;
> @@
> (
> t var = e1;
> <+...
> if (...)
> {
> var = e2;
> ...
> }
> else
> es1
> ...+>
> if ( \( var \| var bo1 e3 \) )
> is2
> else
> es2
> |
> t var
> * = e1
> ;
> ... when != if ( \( var \| var bo2 e4 \) ) is3 else es3
> when != action(..., var, ...)
> when != switch (var) { default: ... }
> when exists
> (
> *e5 = <+... var ...+>
> |
> *var = e5
> )
> )
>
>
> But I stumble on the following error message.
>
> elfring@Sonne:~/Projekte/Linux/next-patched> git checkout next-20190620 && spatch drivers/misc/lkdtm/core.c ~/Projekte/Coccinelle/janitor/show_questionable_variable_initialisation5.cocci
> …
> minus: parse error:
> File "/home/elfring/Projekte/Coccinelle/janitor/show_questionable_variable_initialisation5.cocci", line 36, column 0, charpos = 492
> around = ')',
> whole content = )
>
>
> I observed then that each of the two main branches in the shown SmPL disjunction
> can work as expected. So I wonder even more why the combination can not be parsed
> by the software “Coccinelle 1.0.7-00211-geaa13d59 (OCaml 4.07.1)” so far.
Try
... when any
just before the final ). In some circumstaces the parser doesn't accept
an expression at the end of a sequence like you have here.
julia
[-- Attachment #2: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-06-23 12:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 12:30 [Cocci] Checking redundant variable initialisations with SmPL? Markus Elfring
2019-06-21 20:52 ` Julia Lawall
2019-06-22 13:15 ` Markus Elfring
2019-06-22 13:19 ` Julia Lawall
2019-06-22 13:35 ` Markus Elfring
2019-06-22 13:58 ` Julia Lawall
2019-06-22 14:16 ` Markus Elfring
2019-06-23 7:48 ` Markus Elfring
2019-06-23 12:48 ` Markus Elfring
2019-06-23 12:55 ` Julia Lawall [this message]
2019-06-23 13:05 ` Markus Elfring
2019-06-23 13:05 ` Markus Elfring
2019-06-23 13:13 ` Julia Lawall
2019-06-23 14:17 ` Markus Elfring
2019-06-23 12:48 ` 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.21.1906231454520.4961@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Markus.Elfring@web.de \
--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