2007
DOI: 10.1145/1290520.1290521
|View full text |Cite
|
Sign up to set email alerts
|

Heap reference analysis using access graphs

Abstract: Despite significant progress in the theory and practice of program analysis, analyzing properties of heap data has not reached the same level of maturity as the analysis of static and stack data. The spatial and temporal structure of stack and static data is well understood while that of heap data seems arbitrary and is unbounded. We devise bounded representations that summarize properties of the heap data. This summarization is based on the structure of the program that manipulates the heap. The resulting sum… Show more

Help me understand this report
View preprint versions

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Year Published

2012
2012
2022
2022

Publication Types

Select...
6
4

Relationship

3
7

Authors

Journals

citations
Cited by 37 publications
(12 citation statements)
references
References 41 publications
(55 reference statements)
0
12
0
Order By: Relevance
“…In contrast to these two works, our bottom-up technique addresses aliasing by predicating the results of local analysis on dangerous alias sets. Khedker et al [21] also find SAPs to aid garbage collection. They use a traditional dataflow analysis that is only intra-procedural.…”
Section: Related Workmentioning
confidence: 99%
“…In contrast to these two works, our bottom-up technique addresses aliasing by predicating the results of local analysis on dangerous alias sets. Khedker et al [21] also find SAPs to aid garbage collection. They use a traditional dataflow analysis that is only intra-procedural.…”
Section: Related Workmentioning
confidence: 99%
“…[20] presents a liveness analysis and uses the results for inserting nullifying statements in Java programs. In [29], temporal properties like liveness are checked against an automaton modeling heap accesses.…”
Section: Related Workmentioning
confidence: 99%
“…We initially developed this framework in order to implement heap reference analysis [6] using Soot, because it could not be encoded as an IFDS/IDE problem. However, even with our general framework, performing whole-program analysis turned out to be infeasible due to a large number of interprocedural paths arising from conservative assumptions for targets of virtual calls.…”
Section: The Role Of Call Graphsmentioning
confidence: 99%