In a compiler's storage assignment phase (also called memory allocation within the compiler back end), which responsibilities are included? Select all that apply to a typical language implementation: assigning addresses to user variables, reserving temporaries for intermediate results, and allocating space for literals with proper initialization.

Introduction / Context:
Storage assignment in a compiler (sometimes called memory layout or allocation) maps program objects to specific locations. This includes source-level variables, compiler-generated temporaries, and literal constants that must exist at runtime. Understanding this phase clarifies how compiled code accesses data efficiently and safely.

Given Data / Assumptions:

• A conventional compiled language (for example, PL/I, C, or similar).
• Targets that use stack, static/global areas, and possibly a heap managed by runtime.
• Literals (such as string or numeric constants) may require read-only or static storage with initialization.

Concept / Approach:
The compiler back end assigns addresses or offsets. It lays out activation records for procedures, creates slots for temporaries produced during expression evaluation, and emits data segments for constants. It ensures alignment, size, and lifetime rules are respected (static vs. automatic), often guided by calling conventions and ABI requirements.

Step-by-Step Solution:

Verification / Alternative check:
Inspect generated assembly: look for symbol table entries, .data/.rodata segments for literals, and stack frame (prologue/epilogue) indicating local and temporary allocations.

Why Other Options Are Wrong:

Common Pitfalls:
Confusing runtime heap allocation (done by allocators at execution time) with compile-time storage assignment; overlooking that literals also require addresses and initial contents.

Final Answer:
All of the above.