From: jglisse@redhat.com (Jerome Glisse)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Checking consequences from “exists” usage with big file name selection
Date: Thu, 17 May 2018 10:50:25 -0400 [thread overview]
Message-ID: <20180517145023.GB5048@redhat.com> (raw)
In-Reply-To: <10d2d384-95c0-dec1-b284-f5afb7d9ce81@users.sourceforge.net>
On Thu, May 17, 2018 at 11:11:04AM +0200, SF Markus Elfring wrote:
> > Note i am in no rush, i just wanted to report this as it is likely a bug somewhere
>
> Thanks for your description of a strange software behaviour.
>
> How often do you work with the specification ?exists? in other SmPL scripts?
I need to review all of them but i think i can remove most of them
now that Julia explained that i do not need them if there is no ...
between first match and second match in my rules.
>
>
> > moreover i have a work around.
>
> Is the other transformation approach the solution which is really desired?
My work around was to add function with nested block to an extra
group on which i run the same semantic patch again to take care of
nested block when the original group as two big.
This is a minor inconvenience now that i have found why my semantic
patch was not modifying nested block (took me a while to converge
on the number of files as root of the issue).
Cheers,
J?r?me
next prev parent reply other threads:[~2018-05-17 14:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 19:16 [Cocci] [bug] exists do not work if file group is too big (>49) Jerome Glisse
2018-05-16 19:37 ` Julia Lawall
2018-05-16 19:54 ` Jerome Glisse
2018-05-16 20:02 ` Julia Lawall
2018-05-16 20:15 ` Jerome Glisse
2018-05-16 20:20 ` Julia Lawall
2018-05-16 20:24 ` Jerome Glisse
2018-05-16 20:29 ` Julia Lawall
2018-05-16 20:35 ` Jerome Glisse
[not found] ` <10d2d384-95c0-dec1-b284-f5afb7d9ce81@users.sourceforge.net>
2018-05-17 14:50 ` Jerome Glisse [this message]
[not found] ` <128b6146-5368-12bb-ae42-236982ff3494@users.sourceforge.net>
2018-05-17 14:45 ` [Cocci] exists do not work if file group is too big Jerome Glisse
2018-05-17 20:45 ` Julia Lawall
2018-05-17 21:00 ` Jerome Glisse
2018-05-17 21:11 ` Julia Lawall
2018-05-17 21:32 ` Jerome Glisse
[not found] ` <d1902859-7b9b-4dea-0e5b-8d4876f90495@users.sourceforge.net>
2018-05-18 16:03 ` [Cocci] Checking run times for transformation of Linux source code with SmPL Julia Lawall
[not found] ` <416a7972-d6ce-38b2-9983-ce0446b5ab61@users.sourceforge.net>
2018-05-18 16:49 ` Julia Lawall
[not found] ` <f9b0c961-7182-86ea-bb39-486ffc732db0@users.sourceforge.net>
2018-05-18 17:13 ` Julia Lawall
2018-05-17 20:21 ` [Cocci] [bug] exists do not work if file group is too big (>49) Julia Lawall
2018-05-17 20:31 ` Julia Lawall
2018-05-17 21:04 ` Jerome Glisse
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=20180517145023.GB5048@redhat.com \
--to=jglisse@redhat.com \
--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