From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Run time differences between SmPL disjunctions and regular expressions (in constraints)
Date: Thu, 22 Jan 2015 09:29:19 +0100 [thread overview]
Message-ID: <54C0B4DF.9060203@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1501212342170.2599@hadrien>
> Only use regular expressions if you absolutely have to. They are not
> interpreted when preselecting files, so they drasticaly hurt performance.
How is a file pre-selection involved here?
Would anybody like to compare the concrete run time consequences for the
specification
of a specific function name list in semantic patch scripts?
* Alternation for regular expressions in SmPL constraints
* SmPL disjunction variant
Regards,
Markus
next prev parent reply other threads:[~2015-01-22 8:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 14:05 [Cocci] Matching functions with attributes Eliseo Martínez
2015-01-21 16:15 ` SF Markus Elfring
2015-01-21 17:28 ` Eliseo Martínez
2015-01-21 18:03 ` SF Markus Elfring
2015-01-21 21:36 ` Eliseo Martínez
2015-01-21 21:46 ` Julia Lawall
2015-01-21 22:47 ` Eliseo Martínez
2015-01-22 5:58 ` Julia Lawall
2015-01-22 8:45 ` SF Markus Elfring
2015-01-22 8:59 ` SF Markus Elfring
2015-01-22 9:23 ` Eliseo Martínez
2015-01-22 9:36 ` Eliseo Martínez
2015-01-22 10:11 ` SF Markus Elfring
2015-01-22 11:52 ` Julia Lawall
2015-01-22 12:56 ` Eliseo Martínez
2015-01-22 14:44 ` Julia Lawall
2015-01-22 15:28 ` SF Markus Elfring
2015-01-22 8:29 ` SF Markus Elfring [this message]
2015-01-22 8:37 ` [Cocci] Run time differences between SmPL disjunctions and regular expressions (in constraints) Julia Lawall
2015-01-22 9:50 ` SF Markus Elfring
2015-01-27 19:01 ` [Cocci] Matching functions with attributes 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=54C0B4DF.9060203@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.