From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Improving size determinations with SmPL
Date: Fri, 18 Aug 2017 11:15:49 +0200 [thread overview]
Message-ID: <737c9cf2-5268-6fcf-973f-3a787709c400@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1708181046390.3580@hadrien>
> Here I have the c code,
You have also access to the referenced source files for this Linux software module.
> but not the semantic patch.
I find this kind of feedback surprising.
We discussed it a bit yesterday so that this SmPL script was stored also in
the mailing list archive.
https://systeme.lip6.fr/pipermail/cocci/2017-August/004350.html
> In particular, I don't know whether you are using the version with <... ...>
I am using the optional nest construct for a while also because
> or <+... ...+>.
this SmPL construct does not work for my use case. (I stored a corresponding
test script under an other file name.)
How will the discussion be continued for the bug report ?Get the non-optional
nest construct completely working for SmPL??
https://github.com/coccinelle/coccinelle/issues/114
> The latter is more time consuming because it has to do extra chcks.
I am curious if the software execution can fit better into more pleasing
time ranges.
> Both, however, need to follow the control-flow of the function,
> so they can be expensive if there are many loops or conditionals.
I assume that there are further improvement possibilities available
for the desired run time characteristics.
Regards,
Markus
prev parent reply other threads:[~2017-08-18 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 15:18 [Cocci] Improving size determinations with SmPL SF Markus Elfring
2017-08-17 15:22 ` Julia Lawall
2017-08-17 15:57 ` SF Markus Elfring
2017-08-17 16:00 ` Julia Lawall
2017-08-17 16:11 ` SF Markus Elfring
[not found] ` <alpine.DEB.2.20.1708171818300.3748@hadrien>
2017-08-17 16:50 ` SF Markus Elfring
2017-08-18 8:00 ` SF Markus Elfring
2017-08-18 8:49 ` Julia Lawall
2017-08-18 9:15 ` SF Markus Elfring [this message]
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=737c9cf2-5268-6fcf-973f-3a787709c400@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 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.