1999
DOI: 10.1007/3-540-48294-6_1
|View full text |Cite
|
Sign up to set email alerts
|

A Formal Study of Slicing for Multi-threaded Programs with JVM Concurrency Primitives

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
63
0

Year Published

2000
2000
2023
2023

Publication Types

Select...
4
3
2

Relationship

1
8

Authors

Journals

citations
Cited by 68 publications
(63 citation statements)
references
References 7 publications
0
63
0
Order By: Relevance
“…Note that simulation, arguably more elegant as it is expressed within a very general framework, is in principle a strictly stronger correctness property since it requires observable nodes to execute in the same order, even if they operate on disjoint sets of variables. Hatcliff et al [5] provide a very detailed correctness proof but only consider the case where both executions terminate; for how to deal with non-termination, they refer to [4] which proposes a correctness property based on a variant of bisimulation but does not work out the details. The correctness results by Ranganath et al [9,10], cf.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Note that simulation, arguably more elegant as it is expressed within a very general framework, is in principle a strictly stronger correctness property since it requires observable nodes to execute in the same order, even if they operate on disjoint sets of variables. Hatcliff et al [5] provide a very detailed correctness proof but only consider the case where both executions terminate; for how to deal with non-termination, they refer to [4] which proposes a correctness property based on a variant of bisimulation but does not work out the details. The correctness results by Ranganath et al [9,10], cf.…”
Section: Discussionmentioning
confidence: 99%
“…in [4], that slicing based on ntscd → preserves observable behavior, in particular termination, provided the CFG is reducible (with or without a unique end node). To handle also irreducible CFGs (as is needed to model state charts), [10] proposed several notions of "order dependence", like dod → ("decisive") and wod → ("weak"), and proved that for an arbitrary CFG, slicing based on ntscd → and on dod → preserves observable behavior.…”
Section: Introductionmentioning
confidence: 99%
“…The sliced program is smaller than the original program and is functionally equivalent with respect to the slicing criterion. In this paper, we focus on works that use slicing as a program reduction tool for model checking as shown in Clarke et al (1999), Hatcliff et al (1999), and Millett and Teitelbaum (1998).…”
Section: Static Analysismentioning
confidence: 99%
“…The program slicing library, directly or indirectly, requires various high level analyses such as escape analysis [4], monitor analysis, safe-lock analysis [5], and analyses to calculate and prune various dependences -intra-and inter-procedural data dependence, control [6] dependence, interference [7] dependence, ready dependence and synchronization dependence [5]. These high level analyses rely on low-level information such as object-flow information [8], call graph, and thread graph [4].…”
Section: Indus Java Program Slicermentioning
confidence: 99%