Proceedings of the 37th Annual ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages 2010
DOI: 10.1145/1706299.1706351
|View full text |Cite
|
Sign up to set email alerts
|

Dynamically checking ownership policies in concurrent c/c++ programs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3

Citation Types

0
3
0

Year Published

2010
2010
2014
2014

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 12 publications
(3 citation statements)
references
References 18 publications
0
3
0
Order By: Relevance
“…Another study uses similar concepts to verify programmer-specified ownership policies [27], but that analysis is more restricted in its ability to reason about aliasing and function calls, and it requires programmers to specify when a thread has exclusive access to memory locations, rather than inferring it. Raman et al developed a race condition algorithm for the very different context of structured parallelism, as in Cilk or X10 [33].…”
Section: Related Workmentioning
confidence: 99%
“…Another study uses similar concepts to verify programmer-specified ownership policies [27], but that analysis is more restricted in its ability to reason about aliasing and function calls, and it requires programmers to specify when a thread has exclusive access to memory locations, rather than inferring it. Raman et al developed a race condition algorithm for the very different context of structured parallelism, as in Cilk or X10 [33].…”
Section: Related Workmentioning
confidence: 99%
“…An approach to transferring permissions that is similar to our approach for transferring modes using the annotations acq and rel are the inhale and exhale commands in Chalice [53]. The closest form of assumption to those used in the present paper are the thread-level exclusive ownership (nobody else will read or write) and read ownership policies used in recent work of Martin et al [54]. Ownership is acquired and released via annotations.…”
Section: Related Workmentioning
confidence: 99%
“…In the OO setting, regions are closely related to ownership types which use the class hierarchy of the program to separate the heap into disjoint, nested regions [9,29]. In addition to isolation, ownership types can be used to track effects [8], and to reason about data races and deadlocks [6,4,22]. Such techniques can be used to enforce determinism [30], but regions and ownership relations are not enough to enforce finegrained separation.…”
Section: Related Workmentioning
confidence: 99%