Proceedings of the 2015 Workshop on Partial Evaluation and Program Manipulation 2015
DOI: 10.1145/2678015.2682540
|View full text |Cite
|
Sign up to set email alerts
|

Threads as Resource for Concurrency Verification

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
4
0

Year Published

2017
2017
2023
2023

Publication Types

Select...
3
2

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(4 citation statements)
references
References 22 publications
0
4
0
Order By: Relevance
“…It also allows simple and restrictive forms of scaling permissions which can be applied uniformly over standard predicates. On the other hand, HIP/SLEEK [31] uses rationals to model "thread as resource" so that the ownership of a thread and its resources can be transferred. Chalice [36] has rational permissions to verify properties of multi-threaded, objected-based programs such as data races and dead-locks.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…It also allows simple and restrictive forms of scaling permissions which can be applied uniformly over standard predicates. On the other hand, HIP/SLEEK [31] uses rationals to model "thread as resource" so that the ownership of a thread and its resources can be transferred. Chalice [36] has rational permissions to verify properties of multi-threaded, objected-based programs such as data races and dead-locks.…”
Section: Related Workmentioning
confidence: 99%
“…that there are no dangerous races. Many subsequent program logics [18,20,30,31,45] have introduced increasingly sophisticated notions of "resource disjointness" for the Parallel rule. Fractional permissions (also called "shares") are a relatively simple enhancement to separation logic's original notion of disjointness [4].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…For example, a memory cell can be "fully owned" by a thread, permitting both reading and writing; "partially owned", permitting only reading; or "unowned", permitting nothing; the initial model of fractional shares [8] was rationals in [0, 1]. Since their introduction, many program logics have used a variety of flavors of fractional permissions to verify programs [8,7,33,18,3,37,2,24,38,15,26,14].…”
Section: Introductionmentioning
confidence: 99%