From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Checking statement order for patch generation with SmPL support
Date: Thu, 7 Sep 2017 16:36:50 +0200 [thread overview]
Message-ID: <bf3026c0-f5ac-03bf-0e12-8146f25fcda9@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1709071619340.3168@hadrien>
>> But I have got difficulties to interpret it in an useful way.
>
> Coccinelle follows control-flow paths.
This information is generally fine.
> Thers is a control-flow path from the bottom of a loop back up to the top.
I can not follow with my intermediate understanding to such a view
at the moment.
Why was the combination of a call for the function ?strncmp? before a ?queuefree?
really displayed as an update candidate?
>>> @usage@
>>> identifier action, member, release=~"^.+free$";
>>> expression context,e;
>>> @@
>>> *release(context);
>>> ... when != context = e
>>> when any // to get all results
>>> *action(..., (context)->member, ...)
>>
>> Should the SmPL construct ?<+.. ...+>? work also similar to your suggestion?
>
> <+... ...+> would also not allow context = e after the last match of the
> pattern inside the nest.
This information sounds promising.
I am looking still for possibilities to clarify the overlap better
in the shown functionality.
> A when on a <+... ...+> applies to the entire matched region.
Can the parameter ?when? be combined with this construct anyhow?
Regards,
Markus
next prev parent reply other threads:[~2017-09-07 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 13:10 [Cocci] Checking statement order for patch generation with SmPL support SF Markus Elfring
2017-09-07 13:21 ` Julia Lawall
2017-09-07 13:51 ` SF Markus Elfring
2017-09-07 14:21 ` Julia Lawall
2017-09-07 14:36 ` SF Markus Elfring [this message]
2017-09-07 18:10 ` SF Markus Elfring
2017-09-07 21:26 ` Julia Lawall
2017-09-08 6:58 ` SF Markus Elfring
2017-09-08 7:15 ` 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=bf3026c0-f5ac-03bf-0e12-8146f25fcda9@users.sourceforge.net \
--to=elfring@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 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).