This article may need to be rewritten to comply with Wikipedia's quality standards. Relevant discussion may be found on the talk page. You can help. The talk page may contain suggestions. (July 2014)

In computer science, control-flow analysis (CFA) is a static-code-analysis technique for determining the control flow of a program. The control flow is expressed as a control-flow graph (CFG). For both functional programming languages and object-oriented programming languages, the term CFA, and elaborations such as k-CFA, refer to specific algorithms that compute control flow.^{[dubious – discuss]}

For many imperative programming languages, the control flow of a program is explicit in a program's source code.^{[dubious – discuss]} As a result, interprocedural control-flow analysis implicitly usually refers to a static analysis technique for determining the receivers of function or method calls in computer programs written in a higher-order programming language.^{[dubious – discuss]} For example, in a programming language with higher-order functions like Scheme, the target of a function call may not be explicit: in the isolated expression

(lambda (f) (f x))

it is unclear to which procedure f may refer. A control-flow analysis must consider where this expression could be invoked and what argument it may receive to determine the possible targets.

Techniques such as abstract interpretation, constraint solving, and type systems may be used for control-flow analysis.^{[1][page needed]}

See also

• Control-flow diagram (CFD)
• Data-flow analysis
• Cartesian product algorithm
• Pointer analysis

References

External links

Wikimedia Commons has media related to Control-flow analysis.

• for textbook intraprocedural CFA in imperative languages
• CFA in functional programs (survey)
• for the relationship between CFA analysis in functional languages and points-to analysis in imperative/OOP languages