SPARC Timing
The generic timing model separates architectural sequencing from processor-specific implementation timing.
Tracked events include:
- fetch;
- decode;
- register-window access;
- integer execution;
- branch/delayed transfer;
- load/store;
- FPU operation;
- cache access;
- TLB/translation;
- window spill/fill;
- trap;
- interrupt;
- retirement.
SPARC V9 uses 32-bit instruction words, while actual execution pipelines vary by implementation. citeturn0search20turn0search22
The model does not assign UltraSPARC timing to generic SPARC.
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.