Why Can Programming Languages Invoke System Calls? Is It Due to Compiler‑Generated Machine Code?

Many people mistakenly think that the machine code produced by a compiler has a magical ability to "apply" system calls. In fact, the ability comes from the CPU hardware itself, which provides privileged instructions that switch from user mode to kernel mode.

On x86 the key instruction is int 0x80 or syscall; on ARM it is svc. These are hardware‑level privileged instructions designed specifically to trigger a transition to kernel mode.

When you write a C call such as open("/tmp/test.txt", O_RDONLY), the compiler translates it into a sequence of machine instructions: it places the system‑call number (e.g., 2 for open) into a designated register, loads the arguments (file path, flags) into other registers, and finally executes the syscall instruction.

The CPU sees the syscall instruction, immediately switches to kernel mode, and jumps to the kernel’s pre‑registered handler for that call (e.g., sys_open). After the kernel processes the request, it switches back to user mode and returns the result to the program.

This process is analogous to a citizen filling out a form, ringing a doorbell, and a clerk in a government office handling the request and returning the outcome.

The reason user‑mode programs cannot manipulate hardware directly is security: allowing arbitrary programs to access disks, network cards, or memory would lead to chaos, data loss, and system instability. Therefore the operating system enforces privilege levels, restricting user programs to harmless computations and requiring privileged operations to go through system calls.

In multi‑tasking operating systems like Linux, a “caretaker” (the kernel) coordinates all programs to prevent conflicts. System calls are the service window the kernel provides.

The compiler’s role is simply that of a translator: it converts high‑level language constructs into the machine‑code sequence that includes the privileged switch instruction. The capability itself originates from the CPU, not from the compiler.

Overall, the mechanism involves three layers: the hardware layer (CPU‑provided privileged instructions), the kernel layer (system‑call interface), and the application layer (code generated by the compiler). All three are essential for a system call to work.