# Abstract interpretation

In computer science, **abstract interpretation** is a theory of sound approximation of the semantics of computer programs, based on monotonic functions over ordered sets, especially lattices. It can be viewed as a partial execution of a computer program which gains information about its semantics (e.g., control-flow, data-flow) without performing all the calculations.

Its main concrete application is formal static analysis, the automatic extraction of information about the possible executions of computer programs; such analyses have two main usages:

- inside compilers, to analyse programs to decide whether certain optimizations or transformations are applicable;
- for debugging or even the certification of programs against classes of bugs.

Abstract interpretation was formalized by the French computer scientist working couple Patrick Cousot and Radhia Cousot in the late 1970s.^{[1]}^{[2]}

## Contents

## Intuition[edit]

This section illustrates abstract interpretation by means of real-world, non-computing examples.

Consider the people in a conference room. Assume a unique identifier for each person in the room, like a social security number in the United States. To prove that someone is not present, all one needs to do is see if their social security number is not on the list. Since two different people cannot have the same number, it is possible to prove or disprove the presence of a participant simply by looking up his or her number.

However it is possible that only the names of attendees were registered. If the name of a person is not found in the list, we may safely conclude that that person was not present; but if it is, we cannot conclude definitely without further inquiries, due to the possibility of homonyms (for example, two people named John Smith). Note that this imprecise information will still be adequate for most purposes, because homonyms are rare in practice. However, in all rigor, we cannot say for sure that somebody was present in the room; all we can say is that he or she was *possibly* here. If the person we are looking up is a criminal, we will issue an *alarm*; but there is of course the possibility of issuing a *false alarm*. Similar phenomena will occur in the analysis of programs.

If we are only interested in some specific information, say, "was there a person of age *n* in the room?", keeping a list of all names and dates of births is unnecessary. We may safely and without loss of precision restrict ourselves to keeping a list of the participants' ages. If this is already too much to handle, we might keep only the age of the youngest, *m* and oldest person, *M*. If the question is about an age strictly lower than *m* or strictly higher than *M*, then we may safely respond that no such participant was present. Otherwise, we may only be able to say that we do not know.

In the case of computing, concrete, precise information is in general not computable within finite time and memory (see Rice's theorem and the halting problem). Abstraction is used to allow for generalized answers to questions (for example, answering "maybe" to a yes/no question, meaning "yes or no", when we (an algorithm of abstract interpretation) cannot compute the precise answer with certainty); this simplifies the problems, making them amenable to automatic solutions. One crucial requirement is to add enough vagueness so as to make problems manageable while still retaining enough precision for answering the important questions (such as "may the program crash?").

## Abstract interpretation of computer programs[edit]

Given a programming or specification language, abstract interpretation consists of giving several semantics linked by relations of abstraction. A semantics is a mathematical characterization of a possible behavior of the program. The most precise semantics, describing very closely the actual execution of the program, are called the **concrete semantics**. For instance, the concrete semantics of an imperative programming language may associate to each program the set of execution traces it may produce – an execution trace being a sequence of possible consecutive states of the execution of the program; a state typically consists of the value of the program counter and the memory locations (globals, stack and heap). More abstract semantics are then derived; for instance, one may consider only the set of reachable states in the executions (which amounts to considering the last states in finite traces).

The goal of static analysis is to derive a computable semantic interpretation at some point. For instance, one may choose to represent the state of a program manipulating integer variables by forgetting the actual values of the variables and only keeping their signs (+, − or 0). For some elementary operations, such as multiplication, such an abstraction does not lose any precision: to get the sign of a product, it is sufficient to know the sign of the operands. For some other operations, the abstraction may lose precision: for instance, it is impossible to know the sign of a sum whose operands are respectively positive and negative.

Sometimes a loss of precision is necessary to make the semantics decidable (see Rice's theorem, halting problem). In general, there is a compromise to be made between the precision of the analysis and its decidability (computability), or tractability (complexity).

In practice the abstractions that are defined are tailored to both the program properties one desires to analyze, and to the set of target programs. The first large scale automated analysis of computer programs with abstract interpretation can be attributed to an accident that resulted in the destruction of the first flight of the Ariane 5 rocket in 1996.^{[3]}

## Formalization[edit]

Let *L* be an ordered set, called a **concrete set** and let *L*′ be another ordered set, called an **abstract set**. These two sets are related to each other by defining total functions that map elements from one to the other.

A function α is called an **abstraction function** if it maps an element *x* in the concrete set *L* to an element α(*x*) in the abstract set *L*′. That is, element α(*x*) in *L*′ is the **abstraction** of *x* in *L*.

A function γ is called a **concretization function** if it maps an element *x*′ in the abstract set *L*′ to an element γ(*x*′) in the concrete set *L*. That is, element γ(*x*′) in *L* is a **concretization** of *x*′ in *L*′.

Let *L*_{1}, *L*_{2}, *L*′_{1} and *L*′_{2} be ordered sets. The concrete semantics *f* is a monotonic function from *L*_{1} to *L*_{2}. A function *f*′ from *L*′_{1} to *L*′_{2} is said to be a **valid abstraction** of *f* if for all *x*′ in *L*′_{1}, (*f* ∘ γ)(*x*′) ≤ (γ ∘ *f*′)(*x*′).

Program semantics are generally described using fixed points in the presence of loops or recursive procedures. Let us suppose that *L* is a complete lattice and let *f* be a monotonic function from *L* into *L*. Then, any *x*′ such that *f*(*x*′) ≤ *x*′ is an abstraction of the least fixed-point of *f*, which exists, according to the Knaster–Tarski theorem.

The difficulty is now to obtain such an *x*′. If *L*′ is of finite height, or at least verifies the ascending chain condition (all ascending sequences are ultimately stationary), then such an *x*′ may be obtained as the stationary limit of the ascending sequence *x*′_{n} defined by induction as follows: *x*′_{0}=⊥ (the least element of *L*′) and *x*′_{n+1}=*f*′(*x*′_{n}).

In other cases, it is still possible to obtain such an *x*′ through a widening operator ^{[4]} ∇: for all *x* and *y*, *x* ∇ *y* should be greater or equal than both *x* and *y*, and for any sequence *y*′_{n}, the sequence defined by *x*′_{0}=⊥ and *x*′_{n+1}=*x*′_{n} ∇ *y*′_{n} is ultimately stationary. We can then take *y*′_{n}=*f*′(*x*′_{n}).

In some cases, it is possible to define abstractions using Galois connections (α, γ) where α is from *L* to *L*′ and γ is from *L*′ to *L*. This supposes the existence of best abstractions, which is not necessarily the case. For instance, if we abstract sets of couples (*x*, *y*) of real numbers by enclosing convex polyhedra, there is no optimal abstraction to the disc defined by *x*^{2}+*y*^{2} ≤ 1.

## Examples of abstract domains[edit]

One can assign to each variable *x* available at a given program point an interval [*L*_{x}, *H*_{x}]. A state assigning the value *v*(*x*) to variable *x* will be a concretization of these intervals if for all *x*, *v*(*x*) is in [*L*_{x}, *H*_{x}]. From the intervals [*L*_{x}, *H*_{x}] and [*L*_{y}, *H*_{y}] for variables *x* and *y*, one can easily obtain intervals for *x*+*y* ([*L*_{x}+*L*_{y}, *H*_{x}+*H*_{y}]) and for *x*−*y* ([*L*_{x}−*H*_{y}, *H*_{x}−*L*_{y}]); note that these are *exact* abstractions, since the set of possible outcomes for, say, *x*+*y*, is precisely the interval ([*L*_{x}+*L*_{y}, *H*_{x}+*H*_{y}]). More complex formulas can be derived for multiplication, division, etc., yielding so-called interval arithmetics.^{[5]}

Let us now consider the following very simple program:

y = x; z = x - y;

With reasonable arithmetic types, the result for `z` should be zero. But if we do interval arithmetic starting from `x` in [0, 1], one gets `z` in [−1, +1]. While each of the operations taken individually was exactly abstracted, their composition isn't.

The problem is evident: we did not keep track of the equality relationship between `x` and `y`; actually, this domain of intervals does not take into account any relationships between variables, and is thus a **non-relational domain**. Non-relational domains tend to be fast and simple to implement, but imprecise.

Some examples of **relational** numerical abstract domains are:

- congruence relations on integers
^{[6]}^{[7]} - convex polyhedra
^{[8]}(cf. left picture) – with some high computational costs - difference-bound matrices
^{[9]} - "octagons"
^{[10]}^{[11]}^{[12]} - linear equalities
^{[13]}

and combinations thereof (such as the reduced product ^{[2]}, cf. right picture).

When one chooses an abstract domain, one typically has to strike a balance between keeping fine-grained relationships, and high computational costs.

## Tools[edit]

### Sound tools[edit]

Sound tools guarantee that the verification they perform is correct and exhaustive. They can never yield false negatives, but by undecidability may produce false alarms (or false positive) signaling a potential error with no instance during any execution (because the static analysis is not precise enough to eliminate the potential error).

- AbsInt Advanced Analyzer
^{[14]}^{[15]} - Astrée
- CodeContracts static checker
^{[16]} - CodePeer
- CPAchecker
- ECLAIR
- Fluctuat
- Frama-C value analysis
- IKOS
^{[17]} - Julia Static Analyzer for Java, Android and Java bytecode
^{[18]} - Penjili
^{[19]} - Polyspace
- Predator
^{[20]} - Verasco
^{[21]}

### Unsound tools[edit]

Unsound tools do not guarantee that the verification they perform is correct and exhaustive. They can yield false alarms/positive as well as false negative, not signaling an error that occur for at least one program execution, because the static analysis they perform is incorrect (i.e., they fail to consider some possible executions). As a consequence, they can falsely claim that an unsafe program is safe.

- Codesonar
^{[22]} - Coverity Prevent
- Klocwork Insight
^{[clarification needed]} - Parasoft C/C++test
^{[clarification needed]} - Parasoft Jtest
^{[clarification needed]} - Red Lizard's Goanna
^{[clarification needed]}

## See also[edit]

- Standard interpretation
- Model checking
- Symbolic simulation
- Symbolic execution
- List of tools for static code analysis — contains both abstract-interpretation based (sound) and ad-hoc (unsound) tools
- Static program analysis — overview of analysis methods, including, but not restricted to, abstract interpretation

## References[edit]

**^**Cousot, Patrick; Cousot, Radhia (1977). "Abstract Interpretation: A Unified Lattice Model for Static Analysis of Programs by Construction or Approximation of Fixpoints" (PDF).*Conference Record of the Fourth ACM Symposium on Principles of Programming Languages, Los Angeles, California, USA, January 1977*. ACM Press. pp. 238–252. doi:10.1145/512950.512973.- ^
^{a}^{b}Cousot, Patrick; Cousot, Radhia (1979). "Systematic Design of Program Analysis Frameworks" (PDF).*Conference Record of the Sixth Annual ACM Symposium on Principles of Programming Languages, San Antonio, Texas, USA, January 1979*. ACM Press. pp. 269–282. doi:10.1145/567752.567778. **^**Faure, Christèle. "PolySpace Technologies History". Retrieved 3 October 2010.**^**Cousot, P.; Cousot, R. (August 1992). "Comparing the Galois Connection and Widening / Narrowing Approaches to Abstract Interpretation" (PDF). In Bruynooghe, Maurice; Wirsing, Martin.*Proc. 4th Int. Symp. on Programming Language Implementation and Logic Programming (PLILP)*. Lecture Notes in Computer Science.**631**. Springer. pp. 269–296. ISBN 978-0-387-55844-8.**^**Cousot, Patrick; Cousot, Radhia (1976). "Static determination of dynamic properties of programs" (PDF).*Proceedings of the Second International Symposium on Programming*. Dunod, Paris, France. pp. 106–130.**^**Granger, Philippe (1989). "Static Analysis of Arithmetical Congruences".*International Journal of Computer Mathematics*.**30**: 165–190. doi:10.1080/00207168908803778.**^**Philippe Granger (1991). "Static Analysis of Linear Congruence Equalities Among Variables of a Program". In Abramsky, S.; Maibaum, T.S.E.*Proc. Int. J. Conf. on Theory and Practice of Software Development (TAPSOFT)*. Lecture Notes in Computer Science.**493**. Springer. pp. 169–192.**^**Cousot, Patrick; Halbwachs, Nicolas (January 1978). "Automatic Discovery of Linear Restraints Among Variables of a Program" (PDF).*Conf. Rec. 5th ACM Symp. on Principles of Programming Languages (POPL)*. pp. 84–97.**^**Miné, Antoine (2001). "A New Numerical Abstract Domain Based on Difference-Bound Matrices". In Danvy, Olivier; Filinski, Andrzej.*Programs as Data Objects, Second Symposium, (PADO)*. Lecture Notes in Computer Science.**2053**. Springer. pp. 155–172. arXiv:cs/0703073.**^**Miné, Antoine (Dec 2004).*Weakly Relational Numerical Abstract Domains*(PDF) (Ph.D. thesis). Laboratoire d'Informatique de l'École Normale Supérieure.**^**Antoine Miné (2006). "The Octagon Abstract Domain".*Higher Order Symbol. Comput*.**19**(1): 31–100. arXiv:cs/0703084. doi:10.1007/s10990-006-8609-1.**^**Clarisó, Robert; Cortadella, Jordi (2007). "The Octahedron Abstract Domain" (PDF).*Science of Computer Programming*.**64**: 115–139. doi:10.1016/j.scico.2006.03.009.**^**Michael Karr (1976). "Affine Relationships Among Variables of a Program".*Acta Informatica*.**6**: 133–151. doi:10.1007/BF00268497.**^**Kästner, D.; Ferdinand, C. (2011).*Efficient Verification of Non-Functional Safety Properties by Abstract Interpretation: Timing, Stack Consumption, and Absence of Runtime Errors*. Proceedings of the 29th International System Safety Conference ISSC2011 Las Vegas.**^**AbsInt Advanced Analyzer**^**CodeContracts static checker (cccheck)**^**IKOS**^**Julia Static Analyzer for Java, Android and Java bytecode**^**Penjili**^**predator**^**Verasco**^**Codesonar

## External links[edit]

- A web-page on Abstract Interpretation maintained by Patrick Cousot
- Roberto Bagnara's paper showing how it is possible to implement an abstract-interpretation based static analyzer for a C-like programming language
- The Static Analysis Symposia, proceedings appearing in the Springer LNCS series
- Conference on Verification, Model-Checking, and Abstract Interpretation (VMCAI), affiliated at the POPL conference, proceedings appearing in the Springer LNCS series

- Lecture notes

- Abstract Interpretation. Patrick Cousot. MIT.
- David Schmidt's lecture notes on abstract interpretation
- Møller and Schwarzbach's lecture notes on Static Program Analysis
- Agostino Cortesi's lecture notes on Program Analysis and Verification
- Slides by Grégoire Sutre going through every step of Abstract Interpretation with many examples - also introducing Galois connections