Absolute loading scheme: which traditional loader function is instead handled by the assembler (i.e., performed at assembly time rather than by the loader)?

Introduction / Context:
Different loading schemes distribute responsibilities among assembler, linker, and loader. In an absolute loading scheme, the assembler emits code with fixed absolute addresses, changing the usual division of labor for relocation.

Given Data / Assumptions:

• Absolute loader: places the program into memory without adjusting addresses.
• Assembler knows target starting addresses via origin directives or fixed layout.
• No late binding of external symbols or relocation at load time.

Concept / Approach:
Relocation is the process of adjusting address-sensitive instructions and data when the final load address is determined. In an absolute scheme, the assembler precomputes and fixes addresses; hence the loader does not relocate. The loader simply copies the image to memory and transfers control.

Step-by-Step Solution:

Verification / Alternative check:
Examine object format: absence of relocation records indicates assembler-fixed addresses; the loader has no relocation patches to apply.

Why Other Options Are Wrong:

Common Pitfalls:
Confusing absolute with relocatable or dynamic loading; assuming all loaders must relocate regardless of scheme.

Final Answer:
Relocation of address-sensitive parts.