2012
DOI: 10.1007/978-3-642-30793-5_3
|View full text |Cite
|
Sign up to set email alerts
|

Analysis of May-Happen-in-Parallel in Concurrent Objects

Abstract: Abstract. This paper presents a may-happen-in-parallel (MHP) analysis for OO languages based on concurrent objects. In this concurrency model, objects are the concurrency units such that, when a method is invoked on an object o2 from a task executing on object o1, statements of the current task in o1 may run in parallel with those of the (asynchronous) call on o2, and with those of transitively invoked methods. The goal of the MHP analysis is to identify pairs of statements in the program that may run in paral… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
44
0

Year Published

2012
2012
2023
2023

Publication Types

Select...
6
2

Relationship

2
6

Authors

Journals

citations
Cited by 26 publications
(44 citation statements)
references
References 15 publications
0
44
0
Order By: Relevance
“…Also, it is crucial for improving the accuracy of deadlock, termination and resource analysis. The MHP analysis implemented in SACO [3] can be understood as a function MHP(o p , pp) which returns the set of program points that may happen in parallel with pp when executing in the abstract object o p . A remarkable feature of our analysis is that it performs a local analysis of methods followed by a composition of the local results, and it has a polynomial complexity.…”
Section: Auxiliary Analysesmentioning
confidence: 99%
See 2 more Smart Citations
“…Also, it is crucial for improving the accuracy of deadlock, termination and resource analysis. The MHP analysis implemented in SACO [3] can be understood as a function MHP(o p , pp) which returns the set of program points that may happen in parallel with pp when executing in the abstract object o p . A remarkable feature of our analysis is that it performs a local analysis of methods followed by a composition of the local results, and it has a polynomial complexity.…”
Section: Auxiliary Analysesmentioning
confidence: 99%
“…As regards to related tools, there is another tool [7] which performs deadlock analysis of concurrent objects but, unlike SACO, it does not rely on MHP and points-to analyses. We refer to [3,6] for detailed descriptions on the false positives that our tool can give. Regarding termination, we only know of the TERMINATOR tool [8] for thread-based concurrency.…”
Section: Related Tools and Conclusionmentioning
confidence: 99%
See 1 more Smart Citation
“…It is more flexible than our type system since the assignment of values of different cogs is allowed, but it is less precise than our analysis: consider two objects o 1 and o 2 in a cog c 1 , and another one o 3 in c 2 ; if o 1 calls a method of o 3 which returns o 2 , the type system will not be able to detect that the reference is Near. In [1] the authors present a tool to statically analyze concurrency in ABS. Typically, it analyses the concurrency structure, namely the cogs, but also the synchronization between method calls.…”
Section: Conclusion Future and Related Workmentioning
confidence: 99%
“…Also, we are studying the use of the results gathered by a may-happen-in-parallel analysis [AFMG12] in order to improve the bounds obtained by COSTABS. In particular, if we know that two methods cannot be executing in parallel, we do not have to consider potential interleaving in their executions.…”
Section: Final Remarksmentioning
confidence: 99%