Why Nested subroutine calls in ARM Architecture? - Purpose & Use Cases

The Big Idea

What if you could write a small piece of code once and use it anywhere, even inside other pieces of code?

The Scenario

Imagine writing a program where you have to repeat the same set of instructions multiple times, but each time with a slight variation. Without subroutines, you would have to copy and paste the code everywhere, making it huge and hard to manage.

The Problem

Manually repeating code leads to mistakes, makes debugging a nightmare, and wastes memory. If you want to change something, you must find and update every copy, which is slow and error-prone.

The Solution

Nested subroutine calls let you organize code into small, reusable blocks that can call each other. This keeps programs clean, saves memory, and makes changes easy because you update code in one place.

Before vs After

✗ Before

MOV R0, #5
ADD R0, R0, #3
STR R0, [R1]
; repeated multiple times

✓ After

BL add_five_and_three
STR R0, [R1]
...
add_five_and_three:
  MOV R0, #5
  ADD R0, R0, #3
  BX LR

What It Enables

It enables building complex programs by combining simple tasks, making code easier to read, maintain, and reuse.

Real Life Example

In ARM assembly, a math function can call a subroutine to calculate a value, which itself calls another subroutine to fetch data, creating a chain of nested calls that handle complex operations efficiently.

Key Takeaways

Manual repetition of code is inefficient and error-prone.

Nested subroutine calls organize code into reusable blocks.

This approach simplifies complex programming and maintenance.

Practice

1. What does a nested subroutine call mean in ARM assembly?

easy

A. A subroutine runs without calling any other subroutine

B. A subroutine calls itself repeatedly

C. One subroutine calls another subroutine inside it

D. A subroutine is called only once in the program

Solution

1. Step 1: Understand subroutine calls

   A subroutine is a small program block that can be called to perform a task.

2. Step 2: Define nested calls

   Nested calls happen when one subroutine calls another subroutine inside its code.

3. Final Answer:

   One subroutine calls another subroutine inside it -> Option C

4. Quick Check:

   Nested call = one subroutine calls another [OK]

Hint: Nested means calling a subroutine inside another [OK]

Common Mistakes:

• Confusing nested call with recursion
• Thinking subroutine runs alone without calls
• Mixing up call and return instructions

2. Which ARM instruction is used to call a subroutine?

easy

A. BX LR

B. BL

C. MOV

D. ADD

Solution

1. Step 1: Identify call instruction

   In ARM, the instruction to call a subroutine is 'BL' which means Branch with Link.

2. Step 2: Differentiate from return instruction

   'BX LR' is used to return from a subroutine, not to call it.

3. Final Answer:

   BL -> Option B

4. Quick Check:

   Call subroutine = BL instruction [OK]

Hint: BL calls subroutine; BX LR returns [OK]

Common Mistakes:

• Confusing BX LR as call instead of return
• Using MOV or ADD as call instructions
• Mixing up branch instructions without link

3. Given the following ARM assembly snippet, what is the final value in register R0 after execution?

main:
  MOV R0, #1
  BL sub1
  BX LR

sub1:
  ADD R0, R0, #2
  BL sub2
  BX LR

sub2:
  ADD R0, R0, #3
  BX LR

medium

A. 1

B. 3

C. 0

D. 6

Solution

1. Step 1: Trace main and sub1 execution

   Start with R0=1 in main. Then BL sub1 calls sub1. In sub1, R0 = 1 + 2 = 3.

2. Step 2: Trace sub1 calling sub2

   sub1 calls sub2. In sub2, R0 = 3 + 3 = 6. Then sub2 returns, sub1 returns, main returns.

3. Final Answer:

   6 -> Option D

4. Quick Check:

   1 + 2 + 3 = 6 [OK]

Hint: Add values stepwise through nested calls [OK]

Common Mistakes:

• Ignoring sub2 addition
• Not updating R0 after each call
• Confusing return with call instructions

4. Identify the error in this ARM assembly nested subroutine code:

main:
  BL sub1
  BX LR

sub1:
  ADD R0, R0, #1
  BL sub2
  BX LR

sub2:
  ADD R0, R0, #2
  BX R0

medium

A. Using BX R0 instead of BX LR to return in sub2

B. Missing MOV instruction in main

C. BL should be replaced with BX for calls

D. R0 should not be modified in subroutines

Solution

1. Step 1: Check return instructions

   Subroutines should return using 'BX LR' to jump back to caller address stored in LR.

2. Step 2: Identify incorrect return

   In sub2, 'BX R0' tries to jump to address in R0, which is incorrect and causes error.

3. Final Answer:

   Using BX R0 instead of BX LR to return in sub2 -> Option A

4. Quick Check:

   Return must use BX LR, not BX R0 [OK]

Hint: Return with BX LR, not BX R0 [OK]

Common Mistakes:

• Using BX R0 instead of BX LR
• Confusing BL and BX instructions
• Assuming R0 holds return address

5. You want to organize a complex ARM program by splitting tasks into subroutines that call each other. Which is the best practice for nested subroutine calls to avoid errors?

hard

A. Always use BL to call and BX LR to return, saving LR if calling another subroutine

B. Use BX LR to call and BL to return, no need to save LR

C. Avoid calling subroutines inside subroutines to prevent errors

D. Use MOV to jump between subroutines and ignore LR register

Solution

1. Step 1: Understand call and return instructions

   BL saves return address in LR and branches to subroutine; BX LR returns to caller.

2. Step 2: Handle nested calls safely

   If a subroutine calls another, it must save LR (e.g., on stack) before calling to avoid losing return address.

3. Final Answer:

   Always use BL to call and BX LR to return, saving LR if calling another subroutine -> Option A

4. Quick Check:

   BL call + BX LR return + save LR for nested calls [OK]

Hint: Save LR before nested BL calls, return with BX LR [OK]

Common Mistakes:

• Using BX LR to call instead of BL
• Not saving LR before nested calls
• Jumping with MOV ignoring LR