Why Common subexpression elimination in Compiler Design? - Purpose & Use Cases

The Big Idea

What if your program could spot and skip repeated work all by itself, making it faster instantly?

The Scenario

Imagine you are writing a program by hand and you calculate the same value multiple times in different places, like computing the price of an item with tax repeatedly.

The Problem

Manually repeating the same calculation wastes time and can cause mistakes if you change one place but forget others. It also makes the program slower because the computer does the same work again and again.

The Solution

Common subexpression elimination finds these repeated calculations automatically and replaces them with a single stored result. This saves time and reduces errors without you having to do anything extra.

Before vs After

✗ Before

total1 = price * tax_rate + price
total2 = price * tax_rate + price + shipping_fee

✓ After

temp = price * tax_rate + price
total1 = temp
total2 = temp + shipping_fee

What It Enables

This technique makes programs faster and cleaner by avoiding repeated work behind the scenes.

Real Life Example

When a video game calculates lighting effects many times per frame, common subexpression elimination helps by computing shared parts once, making the game run smoother.

Key Takeaways

Repeated calculations slow down programs and risk errors.

Common subexpression elimination finds and reuses these calculations automatically.

This leads to faster, more reliable programs without extra effort.

Practice

1. What is the main purpose of Common Subexpression Elimination in compiler design?

easy

A. To find repeated calculations and compute them only once

B. To remove unused variables from the code

C. To reorder instructions for parallel execution

D. To translate code into machine language

Solution

1. Step 1: Understand the concept of repeated calculations

   Common subexpression elimination looks for expressions that appear multiple times in code.

2. Step 2: Identify the optimization goal

   It computes these expressions once and reuses the result to save time and work.

3. Final Answer:

   To find repeated calculations and compute them only once -> Option A

4. Quick Check:

   Repeated calculations = compute once [OK]

Hint: Look for repeated expressions to compute once [OK]

Common Mistakes:

• Confusing with dead code elimination
• Thinking it changes instruction order
• Assuming it translates code

2. Which of the following is the correct way to represent a common subexpression elimination in code optimization?

easy

A. Recompute the same expression every time it appears

B. Remove the expression completely from the code

C. Store the result of the expression in a temporary variable and reuse it

D. Replace the expression with a random value

Solution

1. Step 1: Identify the optimization technique

   Common subexpression elimination stores the result of repeated expressions in a temporary variable.

2. Step 2: Understand reuse of stored value

   Later uses of the expression reuse this stored value instead of recomputing.

3. Final Answer:

   Store the result of the expression in a temporary variable and reuse it -> Option C

4. Quick Check:

   Store once, reuse many [OK]

Hint: Store repeated results once to reuse [OK]

Common Mistakes:

• Thinking expressions are removed
• Believing expressions are recomputed every time
• Replacing expressions with unrelated values

3. Consider the code snippet:

a = b + c
d = b + c + e

After applying common subexpression elimination, what is the optimized code?

medium

A. temp = b + c
a = temp
d = temp + e

B. a = b + c
d = b + c + e

C. a = b + c + e
d = b + c + e

D. temp = b + c + e
a = temp
d = temp

Solution

1. Step 1: Identify common subexpression

   The expression b + c appears twice in the code.

2. Step 2: Store and reuse the common expression

   Compute b + c once, store in temp, then use temp for both a and part of d.

3. Final Answer:

   temp = b + c a = temp d = temp + e -> Option A

4. Quick Check:

   Common part stored once =

   temp = b + c
   a = temp
   d = temp + e

   [OK]

Hint: Extract repeated parts into temp variable [OK]

Common Mistakes:

• Not storing the common part
• Storing the entire expression incorrectly
• Duplicating computations

4. Identify the error in the following code after applying common subexpression elimination:

temp = a * b
c = temp + d
temp = a * b + e

medium

A. No error, code is optimized correctly

B. Reassigning temp overwrites previous value causing incorrect reuse

C. The expression a * b is not a common subexpression

D. temp should be declared as a constant

Solution

1. Step 1: Analyze temp variable usage

   The variable temp is assigned a * b first, then reassigned a * b + e.

2. Step 2: Understand impact on reuse

   Reassigning temp overwrites the original value, so reuse of temp later may be incorrect.

3. Final Answer:

   Reassigning temp overwrites previous value causing incorrect reuse -> Option B

4. Quick Check:

   Overwriting temp breaks reuse [OK]

Hint: Avoid overwriting temp holding common subexpression [OK]

Common Mistakes:

• Ignoring reassignment effects
• Assuming temp is constant automatically
• Thinking all expressions are common

5. Given the code:

x = (a + b) * c
y = (a + b) * d
z = (a + b) * c + (a + b) * d

How can common subexpression elimination be applied to optimize this code?

hard

A. temp = (a + b) * (c + d)
x = temp
y = temp
z = temp + temp

B. x = (a + b) * c
y = (a + b) * d
z = x + y

C. temp1 = a + b
z = temp1 * (c + d)
x = z - temp1 * d
y = z - temp1 * c

D. temp = a + b
x = temp * c
y = temp * d
z = x + y

Solution

1. Step 1: Identify common subexpression

   The expression a + b repeats in all calculations.

2. Step 2: Store common subexpression and reuse

   Compute temp = a + b once, then use temp * c and temp * d for x and y. Finally, z = x + y.

3. Final Answer:

   temp = a + b x = temp * c y = temp * d z = x + y -> Option D

4. Quick Check:

   Extract common sum, reuse in products [OK]

Hint: Extract repeated sums first, then multiply [OK]

Common Mistakes:

• Not extracting (a + b) once
• Incorrectly combining terms
• Duplicating calculations