Revision as of 15:31, 27 July 2018 edit Enterprisey (talk \| contribs) Edit filter managers, Autopatrolled, Administrators 34,928 edits →Example: the goto is unnecessary here; undo the float-right ← Previous edit		Revision as of 15:39, 27 July 2018 edit undo Enterprisey (talk \| contribs) Edit filter managers, Autopatrolled, Administrators 34,928 edits I see no original research here; redo first sentences Next edit →
Line 1: In [[~~compiler theory~~compilers]], '''live variable analysis''' (or simply '''liveness analysis''') is a classic [[data-flow analysis]] ~~performed by [[compiler]]s~~ to calculate, ~~for~~at each ~~program~~ point in the program, the [[Variable (programming)\|variables]] that may be potentially read before their next write, that is, the variables that are ''live'' at the exit from each program point.▼ ~~{{original research\|date=September 2017}}~~ ▲In [[compiler theory]], '''live variable analysis''' (or simply '''liveness analysis''') is a classic [[data-flow analysis]] performed by [[compiler]]s to calculate for each program point the [[Variable (programming)\|variables]] that may be potentially read before their next write, that is, the variables that are ''live'' at the exit from each program point. Stated simply: a variable is '''live''' if it holds a value that may be needed in the future.

Live-variable analysis: Difference between revisions