Static single-assignment form: Difference between revisions

Revision as of 16:42, 21 April 2005

Revision as of 02:40, 22 April 2005

Line 101:

* The open source SGI compiler [http://ipf-orc.sourceforge.net/ ORC] uses SSA form in its global scalar optimizer, though the code is brought into SSA form before and taken out of SSA form afterwards. ORC uses extensions to SSA form to represent memory in SSA form as well as scalar values.

* As of summer [[2004]], the [[GNU Compiler Collection]] ishas beingbeen updated to use SSA form. The [[frontend|frontends]]s generate [[GENERIC]] code which is then converted into SSA form by the "[[gimplifier]]" and optimized by the "[[middle-end]]". The [[backend]] eventually translates the optimized intermediate code into [[Register Transfer Language|RTL]], executes some more low-level optimizations and finally turns RTL into [[assembly language]]. The first official release supporting SSA will beis 4.0, tentatively scheduledreleased forin earlyApril [[2005]].

* [[IBM]]'s open source adaptive [[Java virtual machine]], [http://jikesrvm.sourceforge.net/ Jikes RVM], uses Heap Array SSA, an extension of SSA that allows analysis of scalars, arrays, and object fields in a unified framework. Heap Array SSA analysis is only enabled at the maximum optimization level, which is applied to the most frequently executed portions of code.