From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Checking lock usage
Date: Mon, 14 Sep 2015 11:38:00 +0200 [thread overview]
Message-ID: <55F69578.7050100@users.sourceforge.net> (raw)
In-Reply-To: <20150914082905.GA11348@kaficko.joja.cz>
> I want to check whether all accesses to any part of some struct are locked.
I imagine that you will need to perform data-flow analysis for such a task.
I guess that there are some software development challenges to achieve
it with the semantic patch language.
> struct B *b;
> ...
> b->bar->foo;
Are you eventually concerned about the handling of such pointer access
chains?
> If B, I wanted to implement it but got totally lost in the code.
Would you like to increase your efforts for the software development
with the programming language "OCaml"?
Regards,
Markus
next prev parent reply other threads:[~2015-09-14 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 8:29 [Cocci] Find expressions of given type Jan Moskyto Matejka
2015-09-14 9:38 ` SF Markus Elfring [this message]
2015-09-14 14:16 ` Peter Senna Tschudin
2015-09-14 19:46 ` 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=55F69578.7050100@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.