Using this PR as a new feature review (eg not meant to be merged)
Goal: Add precise verilator-like simulation semantics for peak classes and registers
Under this paradigm (only using Register3 for any state), __call__(...) does not ever update state, but only evaluates the combinational logic defined in Peak. The Peak.update_state() method does the state update exactly analogous to toggling the clock in verilator.
In addition, there are set() and get() methods for Regsister3 for to dynamically peak and poke the state.
One ultimate goal is to treat state input/outputs similar to peak outputs/inputs (respectively)for the automatic rewrite rule generation cod generation.
Using this PR as a new feature review (eg not meant to be merged)
Goal: Add precise verilator-like simulation semantics for peak classes and registers
Under this paradigm (only using Register3 for any state),
__call__(...)
does not ever update state, but only evaluates the combinational logic defined in Peak. ThePeak.update_state()
method does the state update exactly analogous to toggling the clock in verilator.To evaluate multiple cycles:
In addition, there are set() and get() methods for Regsister3 for to dynamically peak and poke the state.
One ultimate goal is to treat state input/outputs similar to peak outputs/inputs (respectively)for the automatic rewrite rule generation cod generation.