From: rrh@cs.aau.dk (Rene Rydhof Hansen)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Inter-procedural analysis.
Date: Sun, 23 Dec 2012 00:15:27 +0100 [thread overview]
Message-ID: <20121223001527.1af9e01b@vidarr> (raw)
In-Reply-To: <50D6269D.2060702@gmail.com>
[...]
One other thing you might consider is to first look for functions that
acquire the lock and store the (names of) these functions in a
hashtable, e.g., using the ocaml/python scripting capabilities of
Coccinelle, and then use this hashtable to at least reduce the number
of false positives.
It doesn't solve all problems, but it's quick and easy to do.
/rrh
--
Rene Rydhof Hansen
email: rrh at cs.aau.dk
next prev parent reply other threads:[~2012-12-22 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-22 20:39 [Cocci] Inter-procedural analysis Cyril Roelandt
2012-12-22 20:49 ` Julia Lawall
2012-12-22 21:31 ` Cyril Roelandt
2012-12-22 23:15 ` Rene Rydhof Hansen [this message]
2012-12-23 7:45 ` Julia Lawall
2012-12-23 7:33 ` 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=20121223001527.1af9e01b@vidarr \
--to=rrh@cs.aau.dk \
--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