[Libre-soc-bugs] [Bug 523] demo program needed showing register dependencies

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Fri Nov 13 05:32:03 GMT 2020


https://bugs.libre-soc.org/show_bug.cgi?id=523

--- Comment #22 from Jacob Lifshay <programmerjake at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #20)
> (In reply to Jacob Lifshay from comment #19)
> > (In reply to Luke Kenneth Casson Leighton from comment #17)
> > > the purpose of this bugreport was to aid and assist in evaluating register
> > > allocation strategies, saving considerable time in the hand-writing (4+
> > > hours) of markdown tables through writing extremely rapid prototype and
> > > throw-away one-off python code.
> > 
> > Ok, I had missed that the whole point was to have throw-away code. 
> 
> the purpose is to help speed up the discussion surrounding reg-renaming.
> something that takes 10 days to write has in no way speded up the
> discussion or allowed us to assess and test alternative strategies on a
> one-day cycle.

Once it is more complete, it should be possible to rapidly modify it to test
different algorithms.

> the moment that code-reuse and additional purposes (such as full 
> hardware-level pipeline simulation) is involved, the complexity of the
> resultant code jumps massively, and as such can no longer be considered
> useful as "documentation".

In my opinion it is still effective documentation because it can be
interactively used in a web browser (assuming the web server can transmit
faster than the 2Mbit/s it's currently stuck at and/or enables support for gzip
compression). Once more parts of the algorithms can be adjusted via command
line parameters, it should be quite useful. This is similar to using circuitjs
to document circuits -- people look at the UI, not read the source code.

> ... but this is literally the first time that estimates of time taken
> (based on LoC) is being discussed!
> 
> this should have been discussed *around comment 3*.

Yeah, I get that now.

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


More information about the libre-soc-bugs mailing list