# OpenRISC 1000 Timing Timing events include fetch/decode, register reads, ALU/branch execution, load/store access, pipeline stalls, exceptions, interrupts, and optional extension or cache activity. Pipeline depth and instruction latency vary across implementations. Use measured or documented profile timing; leave unspecified timing unknown rather than inventing cycle counts. ## 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.