You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e8cd3c2
Browse filesBrowse the repository at this point in the historyBrowse files
fix(pipeline): build the out-of-order engine wherever a mode is set
PipelineConfig::apply_to_state assigned the mode field directly, so a
config asking for Scoreboard or Tomasulo + ROB - `raven run --pipeline
--config`, or a config imported in the TUI - got no engine, and the
in-order datapath ran in its place without a word. Copying the config to
the other harts did the same. All three go through set_mode now, and
set_mode builds the engine even when the field was already assigned.
reset_stages and redirect_pc touched only the in-order latches, so under
a dynamic model a reload, a reset or a PC edit left the engine fetching
where the old program was, with its old buffer and statistics. Both now
reach the engine, and a reset also applies the unit counts configured
since it was built. Enabling or disabling the pipeline reaches it too.
With the models really running, riscv-tests passes 71/71 under Tomasulo
+ ROB and 69/71 under Scoreboard; the two failures (rv32uf fcvt, ldst)
come from #86 and from flw/fsw not being ordered as memory accesses.
0 commit comments