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

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Sat May 16 02:45:53 BST 2020


--- Comment #9 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Cole Poirier from comment #8)
> (In reply to Luke Kenneth Casson Leighton from comment #7)
> > (In reply to Cole Poirier from comment #6)
> > you're not.  if the code is unused by anyone (which in this case it is),
> > you cannot cause anyone else "damage" or "inconvenience"... therefore commit
> > it.  right now.
> Indeed I did misunderstand, thank you for correcting me. Unfortunately, I
> just made the correction you suggested, and tried to push but I do not have
> push access rights to the soc repo, only the dev-env-setup repo.

added you.

> Very much so, I agree with your above logic, but due to my misunderstanding
> I was very afraid to commit something because I mistakenly thought it could
> have negative consequences.

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.

> > run python3 bperm.py generate -t il > bperm.il then use yosys to examine the
> > graph (read_ilang bperm.il; show top)
> > 
> > it will be fascinating to see.
> 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".

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.

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

More information about the libre-riscv-dev mailing list