Control flow translation in Compiler Design - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to represent a simple if statement translation.

Compiler Design

if (condition) goto [1];

Drag options to blanks, or click blank then click option'

AL2

BL3

CL1

DL4

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a label that does not correspond to the if block start.

Using a label meant for else or end of if.

The label L2 is used here as the target for the jump when the condition is true, representing the start of the if block.

2fill in blank

medium

Complete the code to translate a while loop control flow.

Compiler Design

[1]: if (!condition) goto L3;

Drag options to blanks, or click blank then click option'

AL4

BL2

CL3

DL1

Attempts:

3 left

💡 Hint

Common Mistakes

Placing the label after the condition check.

Using a label that belongs to the loop body or exit.

The label L1 marks the start of the loop condition check in the while loop translation.

3fill in blank

hard

Fix the error in the translation of an if-else statement by completing the blank.

Compiler Design

if (condition) goto L1;
goto [1];
L1: // if block code

Drag options to blanks, or click blank then click option'

AL1

BL2

CL3

DL4

Attempts:

3 left

💡 Hint

Common Mistakes

Jumping back to the if block label.

Using the same label for both branches.

The jump after the if condition false should go to L2, which marks the else block or code after if.

4fill in blank

hard

Fill both blanks to correctly translate a for loop control flow.

Compiler Design

[1]: if (i >= n) goto [2];

Drag options to blanks, or click blank then click option'

ALstart

BLbody

CLend

DLinit

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing the loop body label with the condition check label.

Using the initialization label as the condition check label.

Lstart marks the loop condition check start, and Lend marks the loop exit point when the condition fails.

5fill in blank

hard

Fill all three blanks to translate an if-else statement with jumps.

Compiler Design

[3]: if (!condition) goto [1];
// if block code
goto [2];
[1]: // else block code
[2]: // code after if-else

Drag options to blanks, or click blank then click option'

ALelse

BLend

CLstart

DLbody

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the else and end labels.

Using the same label for multiple parts.

Lelse is the label for the else block, Lend is the label after the if-else, and Lstart is the start label for the condition check.

Practice

1. What is the main purpose of control flow translation in compiler design?

easy

A. To convert decisions and loops into jumps and labels

B. To optimize memory usage during program execution

C. To translate high-level code into natural language

D. To check syntax errors in the source code

Solution

1. Step 1: Understand control flow translation

   Control flow translation changes decisions (like if-else) and loops into jumps and labels that machines can follow.

2. Step 2: Identify the main purpose

   This process helps convert human-readable code into machine instructions that control program execution order.

3. Final Answer:

   To convert decisions and loops into jumps and labels -> Option A

4. Quick Check:

   Control flow translation = jumps and labels [OK]

Hint: Control flow means changing decisions to jumps [OK]

Common Mistakes:

• Confusing control flow with memory optimization
• Thinking it translates code to natural language
• Mixing it up with syntax checking

2. Which of the following is the correct way to represent an if-else statement in control flow translation?

easy

A. Use function calls instead of jumps

B. Use only unconditional jumps

C. Use variable assignments to control flow

D. Use labels and conditional jumps

Solution

1. Step 1: Recall how if-else is translated

   If-else statements are translated using labels marking code blocks and conditional jumps to decide which block to execute.

2. Step 2: Evaluate options

   Only Use labels and conditional jumps correctly describes using labels and conditional jumps for control flow.

3. Final Answer:

   Use labels and conditional jumps -> Option D

4. Quick Check:

   If-else = labels + conditional jumps [OK]

Hint: If-else needs conditional jumps and labels [OK]

Common Mistakes:

• Using only unconditional jumps loses condition checks
• Thinking function calls replace jumps here
• Confusing variable assignments with control flow

3. Given the pseudo-code:
if (x > 0) { y = 1; } else { y = -1; }
Which control flow translation sequence correctly represents this?

medium

A. label1: if x > 0 jump label2; y = -1; jump label3; label2: y = 1; label3:

B. label1: y = 1; if x > 0 jump label2; y = -1; label2:

C. label1: if x <= 0 jump label2; y = -1; jump label3; label2: y = 1; label3:

D. label1: y = -1; if x <= 0 jump label2; y = 1; label2:

Solution

1. Step 1: Understand the condition and branches

   The condition is if x > 0 then y = 1 else y = -1. So if x > 0 is true, jump to label where y=1.

2. Step 2: Match the correct jump logic

   label1: if x <= 0 jump label2; y = -1; jump label3; label2: y = 1; label3: jumps to label2 if x <= 0 is true, sets y = -1 before jumping to label3, else sets y = 1 at label2.

3. Final Answer:

   label1: if x <= 0 jump label2; y = -1; jump label3; label2: y = 1; label3: -> Option C

4. Quick Check:

   Condition false jumps to y=-1 block [OK]

Hint: Jump on false condition to else block [OK]

Common Mistakes:

• Jumping on true condition instead of false
• Placing assignments before condition check
• Missing jump after true block

4. Identify the error in this control flow translation snippet for the while loop `while (x > 0) { x = x - 1; }`:
label_start: if x == 0 jump label_end; x = x - 1; jump label_start; label_end:

medium

A. The condition should check for x <= 0, not x == 0

B. Missing jump to label_end after decrement

C. Labels are incorrectly placed inside the loop body

D. The decrement operation should be before the condition check

Solution

1. Step 1: Recall correct translation for while(x > 0)

   Correct: label_start: if x <= 0 jump label_end; x = x - 1; jump label_start; label_end:

2. Step 2: Identify the error in condition

   The code checks if x == 0 to jump to end, but for while(x > 0) it should check x <= 0 to exit properly for all non-positive values.

3. Final Answer:

   The condition should check for x <= 0, not x == 0 -> Option A

4. Quick Check:

   Loop condition must correctly end loop [OK]

Hint: Loop condition must cover all exit cases [OK]

Common Mistakes:

• Using equality instead of inequality for loop exit
• Forgetting to jump after decrement
• Misplacing labels causing infinite loops

5. How would you translate a nested if-else inside a loop into control flow statements?

hard

A. Use function calls instead of jumps for nested conditions

B. Use labels for each if-else block and jumps inside the loop to control flow

C. Replace nested if-else with a single unconditional jump

D. Translate only the outer loop and ignore inner if-else

Solution

1. Step 1: Understand nested control flow

   Nested if-else inside loops require multiple labels and conditional jumps to handle each decision point.

2. Step 2: Identify the correct method

   Use labels for each if-else block and jumps inside the loop to control flow accurately represents the standard translation approach.

3. Final Answer:

   Use labels for each if-else block and jumps inside the loop to control flow -> Option B

4. Quick Check:

   Nested control flow = labels + conditional jumps [OK]

Hint: Nested if-else needs labels and jumps [OK]

Common Mistakes:

• Using function calls instead of jumps
• Using only unconditional jumps losing logic
• Ignoring inner conditions in translation