Content deleted Content added
(24 intermediate revisions by 18 users not shown) | |||
Line 1:
{{Short description|Compiler technique}}
{{Cleanup-rewrite|date=July 2014}}
In [[computer science]], '''control
| title = Control-flow analysis in Scheme▼
For many [[imperative programming language]]s, the control flow
<
(lambda (f) (f x))
</syntaxhighlight>
it is unclear to which procedure <code>f</code> may refer. To determine the possible targets, a control-flow analysis must consider where this expression could be invoked, and what argument it may receive.▼
▲it is unclear to which procedure <code>f</code> may refer.
Techniques such as [[abstract interpretation]], [[constraint solving]] and [[type system]]s may be used to compute control-flow analysis{{which}}.<ref>Flemming Nielson, Hanne Riis Nielson & Chris Hankin (1999). ''Principles of Program Analysis''. Springer.</ref>{{pn}}▼
▲Techniques such as [[abstract interpretation]], [[constraint solving]], and [[type system]]s may be used
== See also ==▼
* [[Control-flow diagram]] (CFD)
* [[Cartesian product algorithm]]
* [[Pointer analysis]]
==References==
{{reflist}}
▲[[Category:Control-flow analysis| ]]
{{Commonscat|Control-flow analysis}}
*
*[http://janmidtgaard.dk/papers/Midtgaard-CSur-final.pdf CFA in functional programs (survey)]
*[http://cgi.di.uoa.gr/~smaragd/kcfa-pldi10.pdf for the relationship between CFA analysis in functional languages and points-to analysis in imperative/OOP languages]
{{Compiler optimizations}}
▲== External links ==
▲* http://pages.cs.wisc.edu/~cs701-1/NOTES/3.CONTROL-FLOW-ANALYSIS.html for textbook intraprocedural CFA in imperative languages
|