One kernel, multiple cores
The control path launches work; memory controllers service requests.
Understand the hardware mental model: kernel → blocks → cores → threads → memory. Click any hardware block to discover what it does and where it lives in the RTL.
The control path launches work; memory controllers service requests.
No pipelined instruction overlap. FETCH → DECODE → REQUEST → WAIT → EXECUTE → UPDATE is a sequential control-state machine.
No warp scheduler or scoreboard. The simple core doesn't need out-of-order hazard tracking because it finishes the current instruction before fetching the next.
No branch divergence handling. The scheduler selects next_pc[THREADS_PER_BLOCK-1] as the shared next PC.
No RTL cache in the current src/ list. README discusses caching as a learning direction; the connected design uses memory controllers directly.
Read a short label in the diagram, then find its complete name here. Click any diagram box to inspect its RTL and signals.