Loader functions in absolute loading schemes: In an absolute loader, which function is actually performed by the loader?

Introduction / Context:
Different loader designs provide different services. An absolute loader is the simplest: it takes object code with fixed, absolute addresses and transfers it into memory for execution without performing relocation or linking.

Given Data / Assumptions:

• Input object code already contains absolute addresses.
• All external references have been resolved previously (e.g., by the assembler or a separate linker).

Concept / Approach:
Because addresses are absolute, the loader does not adjust them. It merely reads, verifies, and writes code and data to the specified locations and then starts execution at the given entry point.

Step-by-Step Solution:
Examine capabilities: no relocation records are processed.No symbol resolution across modules occurs at load time.The loader’s task is to load bytes into memory at the addresses already specified.

Verification / Alternative check:
OS and systems programming texts separate absolute loaders from relocating loaders and linkers. Only loading is performed in the absolute scheme.

Why Other Options Are Wrong:
(a) Reallocation/relocation is not done by an absolute loader. (b) Allocation in the sense of dynamic placement is outside its scope. (c) Linking belongs to linkers. (e) Dynamic relocation/binding is a feature of more advanced loaders.

Common Pitfalls:
Assuming every loader links and relocates; absolute loaders are intentionally minimal.

Final Answer:
Loading (placing object code into specified memory addresses).