[libre-riscv-dev] [Bug 64] data handling / io control / data routing API needed

bugzilla-daemon at libre-riscv.org bugzilla-daemon at libre-riscv.org
Sun Apr 28 23:01:44 BST 2019


--- Comment #30 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #29)
> (In reply to Luke Kenneth Casson Leighton from comment #28)
> > jacob i'm going to think for a few days about CombSegFn as despite
> > the potential limitations i like the idea of data being transparently
> > transformed from an input format to an output format.
> Turns out that every single instance where data_i is used it goes directly
> through the Stage.process() function.

 damn.  except in MultiOut (which can be fixed) and MultiIn (which can't).

 MultiIn needs to select the input source *before* processing, otherwise
 it will result in multiple processing blocks being created (one for
 every muxed-in data source) if the data source itself is considered
 to be a transparent self-processing combinatorial block (aka "CombStageFn").

 if however *post* processing was permitted, that would solve the problem.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-riscv-dev mailing list