Why subroutines enable modular assembly code in ARM Architecture - Performance Analysis

Time Complexity: Why subroutines enable modular assembly code

O(n)

Understanding Time Complexity

When using subroutines in ARM assembly, we want to understand how the program's running time changes as we reuse code blocks.

We ask: How does calling subroutines affect the total steps the processor takes?

Scenario Under Consideration

Analyze the time complexity of this ARM assembly code using a subroutine.

    MOV R0, #5          
    BL  subroutine      
    MOV R1, R0          
    
subroutine:
      ADD R0, R0, #1    
      BX  LR            
    

This code calls a subroutine that adds 1 to a value and returns it.

Identify Repeating Operations

Look for repeated instructions or calls.

• Primary operation: The subroutine call (BL) and return (BX LR).
• How many times: Once in this example, but could be many times if called repeatedly.

How Execution Grows With Input

If the subroutine is called multiple times, the total steps grow with the number of calls.

Input Size (calls)	Approx. Operations
10	About 10 subroutine calls plus main instructions
100	About 100 subroutine calls plus main instructions
1000	About 1000 subroutine calls plus main instructions

Pattern observation: The total steps increase roughly in direct proportion to how many times the subroutine is called.

Final Time Complexity

Time Complexity: O(n)

This means the total running time grows linearly with the number of subroutine calls.

Common Mistake

[X] Wrong: "Calling a subroutine adds no extra time because it's just a jump."

[OK] Correct: Each call and return takes extra steps, so more calls mean more total time.

Interview Connect

Understanding how subroutines affect execution time helps you write clear, reusable code while knowing its performance impact.

Self-Check

"What if the subroutine called itself recursively? How would that change the time complexity?"

Practice

1. Why do subroutines help make assembly code modular?

easy

A. They break code into smaller, reusable parts

B. They make the code run faster by default

C. They remove the need for registers

D. They automatically optimize memory usage

Solution

1. Step 1: Understand modularity in code

   Modular code means breaking a program into smaller, manageable pieces that can be reused.

2. Step 2: Role of subroutines in assembly

   Subroutines allow code to be divided into reusable blocks, making it easier to manage and understand.

3. Final Answer:

   They break code into smaller, reusable parts -> Option A

4. Quick Check:

   Modularity = reusable parts [OK]

Hint: Subroutines = reusable code blocks for easier management [OK]

Common Mistakes:

• Thinking subroutines speed up code automatically
• Believing subroutines remove register use
• Assuming subroutines optimize memory without effort

2. Which of the following is the correct way to call a subroutine named process_data in ARM assembly?

easy

A. JMP process_data

B. CALL process_data

C. BL process_data

D. RUN process_data

Solution

1. Step 1: Identify ARM assembly call instruction

   In ARM assembly, the instruction to call a subroutine is BL (Branch with Link).

2. Step 2: Compare options

   Only BL process_data uses BL, which is the correct ARM syntax for calling subroutines.

3. Final Answer:

   BL process_data -> Option C

4. Quick Check:

   ARM subroutine call = BL [OK]

Hint: ARM calls use BL, not CALL or JMP [OK]

Common Mistakes:

• Using CALL which is not ARM syntax
• Using JMP which is for jumps, not calls
• Using RUN which is invalid in assembly

3. Consider this ARM assembly snippet:

BL calculate
MOV R0, #5
BL calculate

What is the main benefit of using the calculate subroutine twice here?

medium

A. It prevents the need for any branching instructions

B. It reduces code duplication by reusing the same code block

C. It avoids using registers for calculations

D. It makes the program run twice as fast automatically

Solution

1. Step 1: Analyze the code snippet

   The subroutine calculate is called twice, showing reuse of the same code block.

2. Step 2: Understand the benefit

   Reusing a subroutine avoids repeating the same instructions multiple times, reducing code size and duplication.

3. Final Answer:

   It reduces code duplication by reusing the same code block -> Option B

4. Quick Check:

   Subroutines reduce duplication [OK]

Hint: Calling subroutines twice reuses code, not speed [OK]

Common Mistakes:

• Assuming calling twice doubles speed
• Thinking registers are not used in subroutines
• Believing subroutines remove all branches

4. You wrote this ARM assembly code to call a subroutine:

BL my_subroutine
MOV R1, #10
BX LR

But the program crashes after returning from my_subroutine. What is the likely error?

medium

A. The subroutine name is case-sensitive and must be uppercase

B. The MOV instruction is invalid after a subroutine call

C. The BX LR instruction should be replaced with BL

D. The subroutine did not preserve the link register (LR) before returning

Solution

1. Step 1: Understand link register usage

   ARM uses the link register (LR) to store return address when calling subroutines with BL.

2. Step 2: Identify common mistake

   If the subroutine modifies LR without saving/restoring it, the return address is lost, causing a crash on BX LR.

3. Final Answer:

   The subroutine did not preserve the link register (LR) before returning -> Option D

4. Quick Check:

   LR must be saved/restored in subroutines [OK]

Hint: Always save LR in subroutines to avoid crashes [OK]

Common Mistakes:

• Thinking MOV after BL causes crash
• Replacing BX LR with BL incorrectly
• Assuming subroutine names are case-sensitive

5. You want to write modular ARM assembly code that calculates the sum of two numbers multiple times with different inputs. Which approach best uses subroutines to achieve this?

hard

A. Write a single subroutine that takes inputs via registers, returns sum in a register, and call it with different values

B. Write separate code blocks for each sum calculation without subroutines

C. Use a subroutine that hardcodes the input values inside it

D. Avoid subroutines and repeat the addition instructions each time

Solution

1. Step 1: Understand modular design for repeated tasks

   Modular code uses subroutines that accept inputs and return outputs to reuse logic flexibly.

2. Step 2: Apply to sum calculation

   A subroutine that takes numbers in registers and returns their sum allows calling it multiple times with different inputs, avoiding code repetition.

3. Final Answer:

   Write a single subroutine that takes inputs via registers, returns sum in a register, and call it with different values -> Option A

4. Quick Check:

   Reusable subroutine with inputs = modular code [OK]

Hint: Use input/output registers in subroutines for flexibility [OK]

Common Mistakes:

• Hardcoding inputs inside subroutines
• Repeating code instead of reusing subroutines
• Avoiding subroutines for repeated calculations