Proceedings of the 18th ACM SIGPLAN-SIGACT Symposium on Principles of Programming Languages - POPL '91 1991
DOI: 10.1145/99583.99599
|View full text |Cite
|
Sign up to set email alerts
|

Pointer-induced aliasing: a problem taxonomy

Abstract: A?iasing occurs at some program point during execution when two or more names exist for the same location. We have isolated various programming language mechanisms which create aliases. We have classified the complexity of the fllas problem induced by each mechanism alone and in combination, as AfP-hard, complement tip-hard, or polynomial ('P). We present our problem classification, give an overview of our proof that finding interprocedural aliases in the presence of single level pointers is in 7, and present … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

3
135
0

Year Published

1995
1995
2015
2015

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 158 publications
(138 citation statements)
references
References 14 publications
3
135
0
Order By: Relevance
“…Our lower bound results follow the tradition set by earlier complexity results due to Landi and Ryder [17] and Muth and Debray [18].…”
Section: Related Worksupporting
confidence: 85%
“…Our lower bound results follow the tradition set by earlier complexity results due to Landi and Ryder [17] and Muth and Debray [18].…”
Section: Related Worksupporting
confidence: 85%
“…For example, imprecise points-to sets can be computed in near linear time, while the computation of flow-and context-sensitive points-to sets is NP-hard [72].…”
Section: Anatomy Of a Source Code Analysismentioning
confidence: 99%
“…The remainder of this section considers points-to analysis as a representative example of a source-code analysis [72,23,116,100]. Points-to analysis was chosen as it is a challenging problem that is an essential precursor to many other source-code analyses.…”
Section: Anatomy Of a Source Code Analysismentioning
confidence: 99%
“…A rich suite of approaches aiming at providing a satisfactory balance between scalability and precision has already been developed in this regard. Examples include: (i) intraprocedural frameworks [16,15] that handle isolated functions only, and their inter-procedural counterparts [15,22,11] that consider the interactions between function calls; (ii) type-based techniques [8]; (iii) flow-based techniques [4,6] that establish aliases depending on the control-flow information of a procedure; (iv) context-(in)sensitive approaches [9,29] that depend on whether the calling context of a function is taken into account or not; (v) field-(in)sensitive approaches [20,1] that depend on whether the individual fields of objects in a program are traced or not. More details on such classifications can be found in [25], for instance.…”
Section: Introductionmentioning
confidence: 99%