From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Software parallelisation?
Date: Fri, 11 Apr 2014 22:55:16 +0200 [thread overview]
Message-ID: <534856B4.8000002@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1404112154260.2064@localhost6.localdomain6>
> Another alternative would be to introduce parallelism within the treatment
> of a single file, eg running a matching rule on each function in parallel.
Are you interested to reuse an evolving software library in the future?
http://stellar.cct.lsu.edu/publications/
Regards,
Markus
next prev parent reply other threads:[~2014-04-11 20:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 17:48 [PATCH] coccinelle: add pycocci wrapper for multithreaded support Luis R. Rodriguez
2014-04-10 17:48 ` [Cocci] " Luis R. Rodriguez
2014-04-10 17:51 ` Johannes Berg
2014-04-10 17:51 ` [Cocci] " Johannes Berg
2014-04-10 17:57 ` Luis R. Rodriguez
2014-04-10 17:57 ` [Cocci] " Luis R. Rodriguez
2014-04-10 19:32 ` Julia Lawall
2014-04-10 19:32 ` Julia Lawall
2014-04-11 8:50 ` [Cocci] Software parallelisation? SF Markus Elfring
2014-04-11 18:49 ` Jesper Louis Andersen
2014-04-11 19:40 ` SF Markus Elfring
2014-04-11 20:04 ` Julia Lawall
2014-04-11 20:42 ` [Cocci] Adjustments for Coccinelle's software build process? SF Markus Elfring
2014-04-11 20:55 ` SF Markus Elfring [this message]
2014-08-28 3:46 ` [Cocci] [PATCH] coccinelle: add pycocci wrapper for multithreaded support Luis R. Rodriguez
2014-08-28 3:46 ` Luis R. Rodriguez
2014-08-28 18:15 ` Julia Lawall
2014-08-28 18:15 ` Julia Lawall
2014-08-28 20:02 ` Luis R. Rodriguez
2014-08-28 20:02 ` Luis R. Rodriguez
2014-04-11 5:55 ` SF Markus Elfring
2014-04-11 5:55 ` [Cocci] " SF Markus Elfring
2014-04-11 6:01 ` Julia Lawall
2014-04-11 6:01 ` Julia Lawall
2014-04-11 6:15 ` SF Markus Elfring
2014-04-11 6:15 ` SF Markus Elfring
2014-04-11 19:00 ` Luis R. Rodriguez
2014-04-11 19:00 ` Luis R. Rodriguez
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=534856B4.8000002@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.