DEC Alpha Timing
Timing model
SLeeLa tracks:
- fetch;
- decode;
- register read;
- issue;
- integer execution;
- FP execution;
- branch prediction/result;
- load/store;
- cache hit/miss;
- TLB;
- dependency stalls;
- exception;
- retirement.
Microarchitectural generations
EV4, EV5, and EV6 have materially different pipeline and issue behavior. EV6's out-of-order, superscalar design requires explicit scheduling and retirement state.
The generic Alpha implementation therefore does not claim one universal cycle count or pipeline depth.
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— Voltages, Variable Clocks, and Expert Timings:SLVoltageRail(actual voltages in mV),SLCpuTiming,SLBusTiming,SLRamTiming,SLIOTiming, the Novice/Basic/Advanced/ExpertSLTimingClasstiers, and theSLTimingProfile->SLTimingManifesta compiled.sleelaimage carries so the compiler/VM honor the declared operating point.lib/cpu/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.