From b20d74887b5c32a0df2f8ada2f5eee4ec457303f Mon Sep 17 00:00:00 2001 From: lkcl Date: Wed, 9 Aug 2023 22:04:10 +0100 Subject: [PATCH] --- 3d_gpu/architecture/inorder_model.mdwn | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/3d_gpu/architecture/inorder_model.mdwn b/3d_gpu/architecture/inorder_model.mdwn index 93318305c..b0679dc0c 100644 --- a/3d_gpu/architecture/inorder_model.mdwn +++ b/3d_gpu/architecture/inorder_model.mdwn @@ -3,19 +3,21 @@ * First steps for a newbie developer [[docs/firststeps]] * bugreport -At present *[Update when this is no longer the case]*, the Libre-SOC core +The Libre-SOC TestIssuer core utilises a Finite-State Machine (FSM) to control the fetch/dec/issue/exec pipelines, with only one pipeline being active at any given time. This is good for debugging the HDL, but severly restricts performance as a single -instruction will take tens of clock cycles to complete. +instruction will take tens of clock cycles to complete. In-development +(Andrey to research and link to the relevant bugreport) is an in-order +core and following on from that will be an out-of-order core. A Single-Issue In-Order control unit will allow every pipepline to be active, and raises the ideal maximum throughput to 1 instruction per clock cycle, bearing any register hazards. -This control unit has not been written in HDL yet, however there's currently a +This control unit has not been written in HDL yet (incorrect: the first version was written 18 months ago, and is in soc/), however there's currently a task to develop the model for the simulator first. The model will be used to -determine performance (and eventually to write the HDL). +determine performance. Diagram that Luke drew comparing pipelines and fsms: -- 2.30.2