Stack frame setup in ARM Architecture

Introduction

A stack frame is a section of the stack that stores information for a function call. Setting it up helps keep track of local variables, return addresses, and function parameters safely.

When a function is called and you need to save the current state before running new code.

When you want to store local variables and function parameters temporarily.

When you need to return to the correct place after a function finishes.

When debugging to understand how functions manage memory.

When writing assembly code for ARM processors to manage function calls.

Core Concept

ARM Architecture

push {fp, lr}
add fp, sp, #4
sub sp, sp, #<local_variable_space>

push {fp, lr} saves the frame pointer and link register on the stack.

add fp, sp, #4 sets the frame pointer to point to the saved frame pointer on the stack.

Key Points

Sets up a stack frame and reserves 16 bytes for local variables.

ARM Architecture

push {fp, lr}
add fp, sp, #4
sub sp, sp, #16

Sets up a stack frame but reserves no space for local variables (empty function).

ARM Architecture

push {fp, lr}
add fp, sp, #4
sub sp, sp, #0

Sets up a stack frame with space for one 4-byte local variable.

ARM Architecture

push {fp, lr}
add fp, sp, #4
sub sp, sp, #4

Detailed Explanation

This ARM assembly program sets up a stack frame with space for two local variables. It stores values 10 and 20 in these local variables, loads them back, adds them, and stores the result in register r4. Finally, it cleans up the stack and returns.

ARM Architecture

    .text
    .global _start

_start:
    push {fp, lr}          @ Save frame pointer and link register
    add fp, sp, #4        @ Set frame pointer
    sub sp, sp, #8        @ Reserve 8 bytes for local variables

    mov r0, #10           @ Example: store 10 in r0
    str r0, [sp, #0]      @ Store r0 at first local variable

    mov r1, #20           @ Store 20 in r1
    str r1, [sp, #4]      @ Store r1 at second local variable

    ldr r2, [sp, #0]      @ Load first local variable into r2
    ldr r3, [sp, #4]      @ Load second local variable into r3

    add r4, r2, r3        @ Add local variables, result in r4

    add sp, sp, #8        @ Clean up local variables
    pop {fp, pc}          @ Restore frame pointer and return

Important Notes

Setting up a stack frame takes constant time, O(1), because it involves a fixed number of instructions.

Space complexity depends on how many local variables you reserve space for on the stack.

A common mistake is forgetting to restore the stack pointer and frame pointer before returning, which can cause crashes.

Use stack frame setup when your function has local variables or calls other functions; for very simple functions, it might be skipped.

Summary

Stack frame setup saves important registers and reserves space for local variables.

It helps keep function calls organized and safe.

Always restore the stack and frame pointers before returning from a function.

Practice

1. What is the primary purpose of setting up a stack frame in ARM architecture during a function call?

easy

A. To save the return address and local variables safely

B. To increase the CPU clock speed

C. To clear all registers before execution

D. To allocate memory for global variables

Solution

1. Step 1: Understand stack frame role

   A stack frame stores important data like return address and local variables for each function call.

2. Step 2: Identify the main purpose

   This setup ensures the function can return correctly and use local data safely.

3. Final Answer:

   To save the return address and local variables safely -> Option A

4. Quick Check:

   Stack frame purpose = Save return address and locals [OK]

Hint: Stack frame saves return address and locals [OK]

Common Mistakes:

• Confusing stack frame with CPU speed control
• Thinking it clears all registers
• Mixing local and global variable storage

2. Which ARM instruction is commonly used to save the link register (return address) onto the stack during stack frame setup?

easy

A. MOV LR, SP

B. POP {LR}

C. PUSH {LR}

D. ADD SP, SP, #4

Solution

1. Step 1: Identify instruction to save LR

   The link register (LR) holds the return address and is saved on the stack using PUSH.

2. Step 2: Match correct instruction

   PUSH {LR} stores LR on the stack; POP {LR} restores it. MOV and ADD do not save LR on stack.

3. Final Answer:

   PUSH {LR} -> Option C

4. Quick Check:

   Save LR with PUSH {LR} [OK]

Hint: Use PUSH to save LR on stack [OK]

Common Mistakes:

• Using POP instead of PUSH to save
• Confusing MOV with stack operations
• Adding to SP instead of saving LR

3. Consider this ARM assembly snippet for function entry:

SUB SP, SP, #16
PUSH {LR}

What is the effect on the stack pointer (SP) after these instructions?

medium

A. SP increases by 16 bytes

B. SP decreases by 16 bytes, then by 4 bytes

C. SP decreases by 20 bytes

D. SP remains unchanged

Solution

1. Step 1: Analyze SUB SP, SP, #16

   This subtracts 16 from SP, moving it down by 16 bytes to allocate space.

2. Step 2: Analyze PUSH {LR}

   PUSH stores LR on stack, which decreases SP by 4 bytes (ARM uses 4-byte words).

3. Final Answer:

   SP decreases by 16 bytes, then by 4 bytes -> Option B

4. Quick Check:

   SP moves down 16 + 4 bytes = 20 bytes total [OK]

Hint: SUB reduces SP, PUSH reduces SP by 4 bytes [OK]

Common Mistakes:

• Adding to SP instead of subtracting
• Ignoring PUSH effect on SP
• Assuming SP stays same after PUSH

4. In this ARM function prologue, what is the error?

SUB SP, SP, #8
POP {LR}

medium

A. LR should not be used in function prologue

B. SUB should add to SP, not subtract

C. SP should not be changed in prologue

D. POP should be PUSH to save LR first

Solution

1. Step 1: Understand stack frame setup order

   Function prologue saves LR by PUSH before changing SP to allocate space.

2. Step 2: Identify incorrect instruction

   POP removes data from stack; here it tries to restore LR before saving it, which is wrong.

3. Final Answer:

   POP should be PUSH to save LR first -> Option D

4. Quick Check:

   Save LR with PUSH before POP [OK]

Hint: Save LR with PUSH before POP [OK]

Common Mistakes:

• Using POP instead of PUSH to save LR
• Changing SP incorrectly
• Ignoring function prologue conventions

5. You want to create a stack frame that saves LR and allocates 24 bytes for local variables. Which sequence correctly sets up the stack frame in ARM assembly?

hard

A. SUB SP, SP, #24
PUSH {LR}

B. PUSH {LR}
SUB SP, SP, #24

C. PUSH {LR, R4}
SUB SP, SP, #20

D. SUB SP, SP, #28
PUSH {LR}

Solution

1. Step 1: Save LR before allocating locals

   Correct order is to allocate space first by subtracting from SP, then save LR with PUSH.

2. Step 2: Check options for correct order and size

   SUB SP, SP, #24 PUSH {LR} subtracts 24 bytes first, then saves LR, which is the correct order to allocate space and save registers.

3. Step 3: Re-examine options carefully

   SUB SP, SP, #24 PUSH {LR}: SUB SP, SP, #24 then PUSH {LR} - correct order and size.
   PUSH {LR} SUB SP, SP, #24: PUSH {LR} then SUB SP, SP, #24 - wrong order.
   PUSH {LR, R4} SUB SP, SP, #20: PUSH {LR, R4} then SUB SP, SP, #20 - wrong registers and size.
   SUB SP, SP, #28 PUSH {LR}: SUB SP, SP, #28 then PUSH {LR} - wrong size.

4. Final Answer:

   SUB SP, SP, #24 PUSH {LR} -> Option A

5. Quick Check:

   Allocate locals first, then save LR [OK]

Hint: SUB SP first to allocate locals, then PUSH LR [OK]

Common Mistakes:

• Allocating space after saving LR
• Using wrong register sets in PUSH
• Mismatching allocated bytes and saved registers