RISC-V Design · All levels

Compressed ISA and Extension Landscape Overview

RISC-V ISA Fundamentals: RISC-V grows from a stable base through modular extensions, with common standards such as M (integer multiply/divide), A (atomics), F/D (floating point), and C (compressed instructions). The compressed extension introduces 16-bit encodings for frequently used operations, improving instruction-cache density and fetch bandwidth efficiency at the cost of added decode expansion logic. Extension selection is product-driven: microcontrollers may prioritize code density and deterministic timing, while application-class cores adopt richer arithmetic, vector, and virtualization capabilities. A key architecture responsibility is maintaining a coherent feature profile across hardware, compiler flags, runtime detection, and operating system expectations. Teams must also manage compatibility boundaries between standard and custom extensions so software remains portable, test coverage remains tractable, and compliance claims remain defensible across silicon revisions.

What this topic teaches

Compressed ISA and Extension Landscape Overview trains mechanism-first reasoning for RISC-V design closure. RISC-V grows from a stable base through modular extensions, with common standards such as M (integer multiply/divide), A (atomics), F/D (floating point), and C (compressed instructions). The compressed extension introduces 16-bit encodings for frequently used operations, improving instruction-cache density and fetch bandwidth efficiency at the cost of added decode expansion logic. Extension selection is product-driven: microcontrollers may prioritize code density and deterministic timing, while application-class cores adopt richer arithmetic, vector, and virtualization capabilities. A key architecture responsibility is maintaining a coherent feature profile across hardware, compiler flags, runtime detection, and operating system expectations. Teams must also manage compatibility boundaries between standard and custom extensions so software remains portable, test coverage remains tractable, and compliance claims remain defensible across silicon revisions.

Senior-engineer framing question

When Code-size reduction from C extension, extension utilization rate, and performance-per-watt impact by workload segment. moves, can you isolate first failing mechanism, request decisive evidence, assign owner, and decide release-safe action?

diagram

RISC-V PIPELINE DIAGRAM - Compressed ISA and Extension Landscape Overview

PC -> IF -> ID -> EX -> MEM -> WB
      |     |      |      |      |
  i-cache decode  ALU/BR  LSU    regfile write
              \   |
               +-> branch resolve + redirect

Hot paths:
  - branch + load-use dependencies in ID/EX
  - memory latency stretching MEM stage
  - writeback arbitration for integer/vector units

Focus: map symptom to first failing stage

Architecture visuals

Draw before you tune. Use these visuals in design reviews, interview loops, and post-silicon triage.

Decode and control map

diagram

DECODE CONTROL MAP - Compressed ISA and Extension Landscape Overview

opcode/funct3/funct7      controls asserted
-----------------------   ---------------------------------------
LUI / AUIPC               rd_write, imm_select(U), alu_add_pc
JAL / JALR                rd_write, pc_redirect, link_write
BRANCH                    cmp_enable, branch_type, pc_redirect
LOAD                      mem_read, rd_write, wb_sel(memory)
STORE                     mem_write, store_size, addr_calc
OP-IMM                    alu_enable, imm_select(I), rd_write
OP                        alu_enable, src2_reg, rd_write
SYSTEM / CSR              csr_readwrite, trap_check, privilege_gate
VECTOR (V extension)      vdecode, lane_mask, vtype_update

Privilege stack

diagram

PRIVILEGE MODE STACK - Compressed ISA and Extension Landscape Overview

            +------------------------------+
            | Machine mode (M)             |
            | firmware, PMP, trap root     |
            +---------------+--------------+
                            |
                    delegated traps
                            v
            +------------------------------+
            | Supervisor mode (S)          |
            | kernel, page tables, drivers |
            +---------------+--------------+
                            |
                    ecall / syscall
                            v
            +------------------------------+
            | User mode (U)                |
            | applications, libraries      |
            +------------------------------+

Key rule: each upward transition records cause + PC in trap CSRs.

Translation path

diagram

MMU PAGE WALK DIAGRAM - Compressed ISA and Extension Landscape Overview

virtual address
    |
    +--> TLB lookup hit? ---- yes ---> physical address -> cache/memory
    |             |
    |             no
    v
satp root PPN + VPN indices
    |
    +--> level-2 PTE fetch (valid?)
    |         |
    |         +-- no -> page fault trap
    v
level-1 PTE fetch -> level-0 PTE fetch
    |
    +--> permissions check (R/W/X, U/S, A/D)
             |
             +-- fail -> access fault trap
             +-- pass -> install TLB entry -> continue

Vector lane lens

diagram

VECTOR LANE VIEW - Compressed ISA and Extension Landscape Overview

VLEN register file
   |
   +--> lane0: ALU/MUL/permute
   +--> lane1: ALU/MUL/permute
   +--> lane2: ALU/MUL/permute
   +--> lane3: ALU/MUL/permute
            ...
mask register -> per-lane predicate enable
load/store unit -> strided/segmented access queue

Throughput model:
effective ops/cycle = active_lanes * issue_rate * mask_density

Focus: balance lane utilization and memory feed

Ownership layers

diagram

RISC-V OWNERSHIP LAYERS - Compressed ISA and Extension Landscape Overview

layer                  owner                         closure artifact
--------------------   ----------------------------  -----------------------------
ISA compliance         architecture/spec team        unpriv + priv test evidence
decode/control         front-end RTL owner           decode matrix + assertions
pipeline timing        microarchitecture owner       hazard/perf regression trends
memory + MMU           LSU/MMU owner                 TLB/pagewalk trace checks
privilege/CSR path     firmware + kernel interface   trap/interrupt conformance
vector subsystem       vector RTL + compiler owner   lane-utilization profiles

Evidence required

Primary metric: Code-size reduction from C extension, extension utilization rate, and performance-per-watt impact by workload segment..
Primary artifact: Extension profile matrix mapping C/M/A/F/D and optional platform features to software requirements, toolchain settings, and compliance tests..
Owners to include: SoC architecture lead, CPU microarchitecture lead, compiler and toolchain owner, OS and platform software owner, product and ecosystem owner.
One reproducible workload and one stable comparator run.
One run with locked environment metadata for causal confidence.

Root-cause tree

diagram

ROOT CAUSE TREE - Compressed ISA and Extension Landscape Overview

Code-size reduction from C extension, extension utilization rate, and performance-per-watt impact by workload segment. regressed
          |
   reproducible on fixed seed?
      /                 \
    no                   yes
    |                     |
env/tool drift       first failing domain?
                     /        |         \
                  decode    execute    memory/MMU
                    |         |            |
               control map  bypass/FU   TLB/walk/perm
                    |
         privilege/CSR side effects checked?

Stop at first confirmed mechanism, then assign explicit owner + fix proof.

Movement trend

diagram

BEFORE / AFTER TREND - Compressed ISA and Extension Landscape Overview

Code-size reduction from C extension, extension utilization rate, and performance-per-watt impact by workload segment.
  ^
  |                           o target band
  |                    o after fix + reruns
  |             o
  |      o baseline (failing)
  +--------------------------------------------------> iteration
       capture issue      isolate mechanism      close + monitor

Use this view to confirm the gain is causal and stable across seeds.

Key takeaways

Classify mechanism before proposing fixes.
Tie every claim to one proving artifact.
Close with owner accountability and rollback criteria.

Common pitfalls

Averaging away tail behavior and mode-specific failures.
Blending results from mismatched build/runtime metadata.
Declaring closure before cross-workload validation.

Practice this lesson