From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, "Richard Henderson" <rth@twiddle.net>,
"Markus Armbruster" <armbru@redhat.com>,
"Nicolas Palix" <nicolas.palix@imag.fr>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Nikunj A Dadhania" <nikunj@linux.vnet.ibm.com>,
"Eric Blake" <eblake@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Michael Tokarev" <mjt@tls.msk.ru>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH v3 1/5] coccinelle: add a script to optimize tcg op using tcg_gen_extract()
Date: Fri, 12 May 2017 09:39:17 +0200 [thread overview]
Message-ID: <d89dcfa9-10a4-561d-7715-926d4930a7b6@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1705121513180.2981@hadrien>
> Even for 6 functions, I would suggest to write out the function names in
> the pattern matching code rather than using regular expressions. If the
> names are explicit, then Coccinelle can do some filtering, either based on
> an index made with idutils or glimpse (see the coccinelle scripts
> directory for tools for making these indices) or based on grep, to drop
> without parsing files that are not relevant. It doesn't do this for
> regular expressions. So you will get a faster result if the names are
> explicit in the pattern code.
Is such filtering performed for source file names?
I would find it more convenient to specify function prefixes as
regular expressions in constraints for the shown SmPL metavariables.
Regards,
Markus
next prev parent reply other threads:[~2017-05-12 7:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 3:35 [Qemu-devel] [PATCH v3 0/5] optimize various tcg_gen() functions using extract op Philippe Mathieu-Daudé
2017-05-12 3:35 ` [Qemu-devel] [RFC PATCH v3 1/5] coccinelle: add a script to optimize tcg op using tcg_gen_extract() Philippe Mathieu-Daudé
2017-05-12 3:41 ` Julia Lawall
2017-05-12 5:36 ` Philippe Mathieu-Daudé
2017-05-12 7:16 ` Julia Lawall
2017-05-12 7:39 ` SF Markus Elfring [this message]
2017-05-12 17:49 ` Eric Blake
2017-05-12 5:48 ` SF Markus Elfring
2017-05-12 11:00 ` SF Markus Elfring
2017-05-12 3:35 ` [Qemu-devel] [PATCH v3 2/5] target/arm: optimize rev16() using extract op Philippe Mathieu-Daudé
2017-05-12 16:50 ` Richard Henderson
2017-05-12 18:21 ` Aurelien Jarno
2017-05-12 19:05 ` Richard Henderson
2017-05-12 19:22 ` Aurelien Jarno
2017-05-12 19:38 ` Richard Henderson
2017-05-12 23:50 ` Philippe Mathieu-Daudé
2017-05-12 3:35 ` [Qemu-devel] [PATCH v3 3/5] target/m68k: optimize bcd_flags() " Philippe Mathieu-Daudé
2017-05-12 3:35 ` [Qemu-devel] [PATCH v3 4/5] target/ppc: using various functions " Philippe Mathieu-Daudé
2017-05-12 23:48 ` Philippe Mathieu-Daudé
2017-05-12 3:35 ` [Qemu-devel] [PATCH v3 5/5] target/sparc: optimize " Philippe Mathieu-Daudé
2017-05-12 23:49 ` Philippe Mathieu-Daudé
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=d89dcfa9-10a4-561d-7715-926d4930a7b6@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=armbru@redhat.com \
--cc=aurelien@aurel32.net \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=julia.lawall@lip6.fr \
--cc=lvivier@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=nicolas.palix@imag.fr \
--cc=nikunj@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).