Seventh IEEE International Working Conference on Source Code Analysis and Manipulation (SCAM 2007) 2007
DOI: 10.1109/scam.2007.26
|View full text |Cite
|
Sign up to set email alerts
|

Towards Path-Sensitive Points-to Analysis

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2011
2011
2016
2016

Publication Types

Select...
4
2

Relationship

2
4

Authors

Journals

citations
Cited by 7 publications
(7 citation statements)
references
References 25 publications
0
7
0
Order By: Relevance
“…Symbolic pointer analysis has been discussed in the literature [17][18][19]32]. Zhu [18] used a boolean function represented by BDD to capture the program state of a procedure, while BDDs are known to suffer from exponential blow-up on multiplication, division, which are all frequent operation in programs.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Symbolic pointer analysis has been discussed in the literature [17][18][19]32]. Zhu [18] used a boolean function represented by BDD to capture the program state of a procedure, while BDDs are known to suffer from exponential blow-up on multiplication, division, which are all frequent operation in programs.…”
Section: Related Workmentioning
confidence: 99%
“…Zhu [18] used a boolean function represented by BDD to capture the program state of a procedure, while BDDs are known to suffer from exponential blow-up on multiplication, division, which are all frequent operation in programs. Gutzmann [32] suggested a new way to achieve path-sensitive pointer analysis, but it might lead to an unacceptably low absolute performance. One of the most related work with ours is [17], in which the symbolic evaluation technique was used to handling heap algebra for detecting memory leaks, but the symbolic heap algebra and the pointer graph reachability algorithm were somehow too complicate and with a poor efficiency; our STVL not only supports the heap memory abstraction, but also naturally supports the pointer arithmetic and alias analysis.…”
Section: Related Workmentioning
confidence: 99%
“…al [23] present an approach that retains control-flow information by inserting path-specific filter operations in the program dataflow. The filter operations correspond to different types of branching conditions in the control flow.…”
Section: Points-to Analysismentioning
confidence: 99%
“…In addition to the upper bounds from automated feedback, we allow even coarse grained hints which are more accessible to human insight, i.e., (1) which code can be considered dead, (2) what arguments to or return values of methods are infeasible, (3) what call relations can not be taken. Figure 3.1 shows a short example code of where such manual feedback is trivial but which many points-to analysis algorithms cannot deduct: (1) The user is able to prove that method f () never returns −1, so that the code at line 6 can be considered dead.…”
Section: Manual Feedbackmentioning
confidence: 99%
“…For future work, it should be possible to perform this optimization automatically by inserting special filter-operations (cf. [2]) into the analysis' program representation.…”
Section: Polymorphic Calls In Branching Conditionsmentioning
confidence: 99%