Live variable analysis in Compiler Design - Step-by-Step Execution

Concept Flow - Live variable analysis

Start at end of program

↓

Initialize live variables as empty

↓

For each statement backward

↓

Remove variables defined here

↓

Add variables used here

↓

Update live variable set

↓

Repeat for all statements

↓

Result: live variables at each point

Live variable analysis works backward through code, tracking which variables are needed later by removing those redefined and adding those used.

Execution Sample

Compiler Design

1: a = 5
2: b = a + 1
3: a = 3
4: c = a + b
5: print(c)

Analyze live variables backward from line 5 to line 1.

Analysis Table

Step	Statement	Live Variables Before	Variables Defined	Variables Used	Live Variables After
1	print(c)	{}	{}	{c}	{c}
2	c = a + b	{c}	{c}	{a,b}	{a,b}
3	a = 3	{a,b}	{a}	{}	{b}
4	b = a + 1	{b}	{b}	{a}	{a}
5	a = 5	{a}	{a}	{}	{}

💡 Reached start of program; live variables at start are empty.

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
a	undefined	undefined	present	removed	present	removed
b	undefined	undefined	present	present	removed	removed
c	undefined	present	removed	removed	removed	removed

Key Insights - 3 Insights

Why do we remove a variable from the live set when it is defined?

Because defining a variable means its old value is overwritten, so the previous value is no longer needed. See step 3 in execution_table where 'a' is removed after being defined.

Why do we add variables used in a statement to the live set?

Variables used are needed for the current computation, so they must be live before this statement. For example, at step 2, 'a' and 'b' are added because they are used.

Why does the analysis proceed backward through the code?

Because we want to know which variables are needed in the future, so we start from the end and move backward to see what must be kept alive.

Visual Quiz - 3 Questions

Look at the execution_table at step 3. Which variable is removed from the live set after this step?

A b

B a

C c

D none

💡 Hint

Check the 'Live Variables After' column at step 3 in execution_table.

At which step does variable 'c' stop being live?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at when 'c' disappears from the live variables in execution_table rows.

If variable 'b' was not used in statement 4, how would the live variables after step 4 change?

A b would be removed

B a would be removed

C b would remain live

D no change

💡 Hint

Refer to step 4 in execution_table and consider the effect of usage on live variables.

Concept Snapshot

Live Variable Analysis:
- Works backward through code
- Removes variables when defined (overwritten)
- Adds variables when used
- Tracks variables needed in future
- Helps optimize by identifying unused values

Full Transcript

Live variable analysis is a method used in compiler design to find which variables hold values that will be used later in the program. It works by starting at the end of the program and moving backward through each statement. At each step, variables that are defined (assigned new values) are removed from the live set because their old values are no longer needed. Variables that are used (read) are added to the live set because their values are needed for computation. This process continues until the start of the program is reached, resulting in a set of live variables at each point. This helps compilers optimize code by knowing which variables can be safely discarded or reused.