Why Subroutine call convention (AAPCS) in ARM Architecture? - Purpose & Use Cases

The Big Idea

What if every function call in your program was a mystery box you had to carefully open and close yourself?

The Scenario

Imagine writing a program where every time you call a small task (subroutine), you have to remember exactly which registers to save and restore yourself, and how to pass each piece of data manually.

Without a clear rulebook, your code becomes a confusing mess, and different parts of your program might not work well together.

The Problem

Manually managing which registers to save or restore is slow and error-prone.

You might overwrite important data or cause crashes because one part of the program expects data in a certain place, but another part changed it unexpectedly.

This makes debugging very hard and wastes time.

The Solution

The AAPCS (ARM Architecture Procedure Call Standard) sets clear rules for how subroutines should pass arguments, use registers, and return values.

This standard ensures every part of the program agrees on how to communicate, making code reliable and easier to maintain.

Before vs After

✗ Before

push {r0, r1}
mov r0, #5
bl some_function
pop {r0, r1}

✓ After

bl some_function  ; AAPCS ensures r0-r3 used for args, r0 for return

What It Enables

It enables smooth, predictable communication between different parts of a program and even between different programs or libraries on ARM devices.

Real Life Example

When your smartphone runs apps, the operating system and apps use AAPCS to call functions safely and efficiently without crashing or mixing up data.

Key Takeaways

Manual register management is complex and risky.

AAPCS provides a clear, shared set of rules for subroutine calls.

This makes ARM programs more reliable and easier to build and maintain.