From: Julia Lawall <julia.lawall@lip6.fr>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Checking influence of loops?
Date: Sat, 13 Apr 2019 18:03:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1904131802270.2536@hadrien> (raw)
In-Reply-To: <566b0019-021a-0415-4b98-b5d8c74beb83@web.de>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Sat, 13 Apr 2019, Markus Elfring wrote:
> >>>>> Your ifs may be in a loop.
> >>>>
> >>>> Does your technology treat this control flow in special ways?
> >>>
> >>> No.
> >>
> >> Would the quoted information be irrelevant then for the discussed use case?
> >
> > No idea what the above means.
>
> It seems that there is another communication difficulty involved.
>
> Your feedback indicated concerns for the handling of loops
> in the shown source code search results, didn't it?
>
>
> > There are control flow paths that cause ... to connect things.
>
> I guess that these “connections” need further clarifications.
>
>
> > The process of matching doesn't know if the connection is due to a loop,
> > and if, a goto, or anything else.
>
> Should two search specifications (with SmPL ellipses) between them
> be kept separate for the desired diff output?
I don't understand any of your answers precisely.
If you have a pattern like
AAA
...
BBB
The AAA and BBB might match the same code if there is a possible flow of
execution from the match of AAA to itself.
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-04-13 16:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 15:23 [Cocci] Searching for duplicate statements in if branches (with SmPL)? Markus Elfring
[not found] ` <alpine.DEB.2.20.1904111728380.3143@hadrien>
2019-04-11 15:43 ` Markus Elfring
[not found] ` <alpine.DEB.2.20.1904111749350.3143@hadrien>
2019-04-11 16:00 ` Markus Elfring
2019-04-12 7:09 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1904120912270.2733@hadrien>
2019-04-12 7:43 ` Markus Elfring
2019-04-13 15:36 ` [Cocci] Checking influence of loops? Markus Elfring
[not found] ` <alpine.DEB.2.21.1904131737540.2536@hadrien>
2019-04-13 15:42 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1904131743330.2536@hadrien>
2019-04-13 15:53 ` Markus Elfring
2019-04-13 16:03 ` Julia Lawall [this message]
2019-04-13 16:11 ` Markus Elfring
2019-04-13 16:16 ` Julia Lawall
2019-04-13 16:28 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1904131834510.2536@hadrien>
2019-04-13 16:46 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1904131905320.2536@hadrien>
2019-04-13 17:29 ` [Cocci] Clarification for SmPL ellipsis functionality Markus Elfring
2019-04-14 7:42 ` [Cocci] Clarification for SmPL functionality around position variables Markus Elfring
2019-04-14 7:47 ` Julia Lawall
2019-04-14 8:02 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1904141006320.2615@hadrien>
2019-04-14 8:21 ` Markus Elfring
[not found] ` <alpine.DEB.2.21.1904141023450.2615@hadrien>
2019-04-14 8:27 ` 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.1904131802270.2536@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;
as well as URLs for NNTP newsgroup(s).