[libre-riscv-dev] [Bug 316] bperm TODO

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Sat May 16 03:03:12 BST 2020


--- Comment #10 from Cole Poirier <colepoirier at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #9)
> (In reply to Cole Poirier from comment #8)
> added you.

Awesome! It worked :)

> think in terms of multi-way collaboration: you need to do work, other people
> need to do work, the code under development needs to work.
> the guidelines (based on 20+ years of experience of working with software
> libre) balance all those three things.

I'm with you fully Luke. I try to follow your guidelines as best as I can.

> > Ohhhboy... It worked! Very cool, however it is indeed a monster of a design
> yyep.  to be expected.  clifford's bperm code is equally massive.
> you might want to try running these:
> * proc
> * opt
> * show top
> and if you *really* want to put your computer into meltdown, run "synth"
> followed by "show top".

I just might try it.

> just from a few lines of python, eh?  shows how careful you have to be
> when working in H(igh) D(efinition) L(anguage)s.

It really is incredible. Looking forward to improving the level of care I am
capable of taking with regard to HDL.

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

More information about the libre-riscv-dev mailing list