# RISC-V Timing RISC-V specifies architectural behavior while leaving most pipeline timing to the implementation. SLeeLa records: - instruction fetch; - decode; - register read; - execute; - memory access; - extension-unit latency; - dependency stalls; - branch prediction/result; - cache hit/miss; - TLB/page-table walk; - exception/interrupt; - retirement. ## Instruction alignment The base RV32I ISA uses 32-bit instructions and IALIGN=32. An instruction extension supporting 16-bit instructions can relax alignment to IALIGN=16. citeturn0search0 ## Microarchitectural profiles Single-cycle, multicycle, in-order pipeline, superscalar, speculative, and out-of-order implementations can be represented without changing the ISA model. ## Expert timing, voltages, and variable clocks (shared across all CPU models) The per-CPU timing above is the architectural/behavioral view for this part. The adjustable, quality-first timing system is shared by every CPU model in `lib/cpu` and is documented once, in the package guide: - [`lib/cpu/TIMING.md`](../../TIMING.md) — Voltages, Variable Clocks, and Expert Timings: `SLVoltageRail` (actual voltages in mV), `SLCpuTiming`, `SLBusTiming`, `SLRamTiming`, `SLIOTiming`, the Novice/Basic/Advanced/Expert `SLTimingClass` tiers, and the `SLTimingProfile` -> `SLTimingManifest` a compiled `.sleela` image carries so the compiler/VM honor the **declared** operating point. - [`lib/cpu/components/README.md`](../../components/README.md) — running a CPU at spec and **overclocking** it (`SLClockPolicy` / `setSpecClock` / `overclock`), plus the RAM / storage / optical / system-bus parts bin and the DMA / GPU / native-RAM options. Every CPU model (this one included) inherits the clock/overclock surface from `SLCPURuntime` and can be assembled with those shared expert-timing, voltage, and component options; they are a build-layer concern, not re-declared per CPU.