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

[bugzilla-daemon at libre-riscv.org]

http://bugs.libre-riscv.org/show_bug.cgi?id=64

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Jacob Lifshay from comment #1)
> see
> https://salsa.debian.org/Kazan-team/simple-barrel-processor/blob/master/src/
> PipelineBuildingBlockAPIProposal.py for a WIP API proposal.
> 
> Which API design to use is not resolved yet.

yes. and names need to be agreed.  there's been a lot of confusion
resulting from names that have multiple potential meanings.

the other design is here:
*
https://git.libre-riscv.org/?p=ieee754fpu.git;a=blob;f=src/add/singlepipe.py;h=fe052be72a3e70fde85e56058cf708ea9e7cd341;hb=25a0ec563bd7837b43a1d04036b2a5945c97023b
*
https://git.libre-riscv.org/?p=ieee754fpu.git;a=blob;f=src/add/multipipe.py;h=35da5c2ec741aafc66e97804e842be0395b8a863;hb=25a0ec563bd7837b43a1d04036b2a5945c97023b

this design is already in use (in the IEEE754 FPU) which implies that
changes need to be handled very carefully in an incremental fashion,
to keep all unit tests operational at all times.

review of each is needed (TBD separate comment).

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