2015
DOI: 10.1007/978-3-662-47666-6_25
|View full text |Cite
|
Sign up to set email alerts
|

Owicki-Gries Reasoning for Weak Memory Models

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
89
0

Year Published

2017
2017
2020
2020

Publication Types

Select...
6
1
1

Relationship

1
7

Authors

Journals

citations
Cited by 76 publications
(90 citation statements)
references
References 15 publications
0
89
0
Order By: Relevance
“…Therefore, similar to [33], it is unclear how to handle the program with dependencies across loop iterations introduced in Section 1. Similarly, since no program in Lahav et al's paper, which performed Owicki-Gries reasoning for weak memory models, contains multiple statements except SK [27], it is never clear how to handle dependencies across loop iterations. In addition, they did not show their completeness.…”
Section: Related Workmentioning
confidence: 99%
“…Therefore, similar to [33], it is unclear how to handle the program with dependencies across loop iterations introduced in Section 1. Similarly, since no program in Lahav et al's paper, which performed Owicki-Gries reasoning for weak memory models, contains multiple statements except SK [27], it is never clear how to handle dependencies across loop iterations. In addition, they did not show their completeness.…”
Section: Related Workmentioning
confidence: 99%
“…This can be achieved by either extending existing program logics for weak memory, or developing new program logics for currently unsupported models. In particular, we can reason about the PSI models presented here by developing custom proof rules in the existing program logics for RA such as [22,39].…”
Section: Discussionmentioning
confidence: 99%
“…First, uses the Owicki-Gries method [29] to verify concurrent programs. These methods are unsound for weak memory models [22], so , and hence our proofs, assume a sequentially-consistent memory model. Second, 's strategy for building the simulation relation requires implementations to have statically-known linearization points because it checks that there exists exactly one atomic section in each code path where the global state is modi ed, and this modi cation is simulated by the speci cation.…”
Section: Implementation and Evaluationmentioning
confidence: 99%