Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 208] implement CORDIC in a general way sufficient to do transcendentals
From: bugzilla-daemon @ 2020-04-20 21:51 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-208-13@https.bugs.libre-soc.org/>

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

--- Comment #34 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
this may also help to understand IEEE754 FP
https://imgs.xkcd.com/comics/garbage_math.png

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-20 22:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #70 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #68)
> how come i manage to break things all the time??
> https://gitlab.lip6.fr/vlsi-eda/coriolis/-/issues/9
> :)

That's half a bug ;-). Put a breakpoint just before the final routing
stage, to see the placement. You will see that it is broken.

In particular, no cell must be outside the abutment box for the
routing to work. It shouldn't end up in core dump, but it issue
a lot of warning/erros before. Especially the "No GCell under"
which means that something to connect to is outside the AB, that
must never happens.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] [Bug 208] implement CORDIC in a general way sufficient to do transcendentals
From: Jacob Lifshay @ 2020-04-20 22:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-208-13-iyPdEi6O5A@https.bugs.libre-soc.org/>

On Mon, Apr 20, 2020, 14:51 <bugzilla-daemon@libre-soc.org> wrote:

> https://bugs.libre-soc.org/show_bug.cgi?id=208
>
> --- Comment #34 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
> this may also help to understand IEEE754 FP
> https://imgs.xkcd.com/comics/garbage_math.png


Ooh, nice! Garbage in -> modified garbage out.

well, if you want to learn Python:
https://xkcd.com/353/

(try running the referenced command in an actual python interpreter)

Jacob
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 290] New: import error caused by soc.decoder.isa.all no longer being generated
From: bugzilla-daemon @ 2020-04-21  2:11 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 290
           Summary: import error caused by soc.decoder.isa.all no longer
                    being generated
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: normal
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: programmerjake@gmail.com
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

This is causing CI to fail and I finally got around to reproducing it locally:

After running git clean and rerunning src/doc/decoder/pseudo/pywriter.py:

ERROR: Failure: ModuleNotFoundError (No module named 'soc.decoder.isa.all')
----------------------------------------------------------------------
Traceback (most recent call last):
  File
"/home/jacob/.virtualenvs/libre-riscv-venv/lib/python3.6/site-packages/nose/failure.py",
line 39, in runTest
    raise self.exc_val.with_traceback(self.tb)
  File
"/home/jacob/.virtualenvs/libre-riscv-venv/lib/python3.6/site-packages/nose/loader.py",
line 418, in loadTestsFromName
    addr.filename, addr.module)
  File
"/home/jacob/.virtualenvs/libre-riscv-venv/lib/python3.6/site-packages/nose/importer.py",
line 47, in importFromPath
    return self.importFromDir(dir_path, fqname)
  File
"/home/jacob/.virtualenvs/libre-riscv-venv/lib/python3.6/site-packages/nose/importer.py",
line 94, in importFromDir
    mod = load_module(part_fqname, fh, filename, desc)
  File "/home/jacob/.virtualenvs/libre-riscv-venv/lib/python3.6/imp.py", line
235, in load_module
    return load_source(name, filename, file)
  File "/home/jacob/.virtualenvs/libre-riscv-venv/lib/python3.6/imp.py", line
172, in load_source
    module = _load(spec)
  File "<frozen importlib._bootstrap>", line 684, in _load
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File
"/home/jacob/projects/libreriscv/soc/src/soc/decoder/isa/test_caller.py", line
12, in <module>
    from soc.decoder.isa.all import ISA
ModuleNotFoundError: No module named 'soc.decoder.isa.all'


I'm on soc.git d557f4fb2a9e5b159c7abbdcd1d85712fabc6b9b

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 290] import error caused by soc.decoder.isa.all no longer being generated
From: bugzilla-daemon @ 2020-04-21  3:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-290-13@https.bugs.libre-soc.org/>

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
it's autogenerated, so make something has to be run as part of the setup. 4am
now will look later.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 290] import error caused by soc.decoder.isa.all no longer being generated
From: bugzilla-daemon @ 2020-04-21  3:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-290-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Jacob Lifshay <programmerjake@gmail.com> ---
To clarify, the error is triggered by running nosetests, pywriter.py completes
successfully.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 290] import error caused by soc.decoder.isa.all no longer being generated
From: bugzilla-daemon @ 2020-04-21  3:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-290-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/decoder/pseudo/pywriter.py;h=7a1c3f5ec22fcd0aa675963ab385007ad82c1b4e;hb=HEAD#l116

commented out.  moo?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 290] import error caused by soc.decoder.isa.all no longer being generated
From: bugzilla-daemon @ 2020-04-21  4:01 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-290-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/decoder/pseudo/pywriter.py;h=7a1c3f5ec22fcd0aa675963ab385007ad82c1b4e;hb=HEAD#l116
> 
> commented out.  moo?

commented out in
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=ade28272f9845d8eec21895a31c1b6ca012488ba

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 290] import error caused by soc.decoder.isa.all no longer being generated
From: bugzilla-daemon @ 2020-04-21  4:28 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-290-13@https.bugs.libre-soc.org/>

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

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
that was a mistake when i added extra registers

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 290] import error caused by soc.decoder.isa.all no longer being generated
From: bugzilla-daemon @ 2020-04-21  4:48 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-290-13@https.bugs.libre-soc.org/>

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

Jacob Lifshay <programmerjake@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #5)
> that was a mistake when i added extra registers

Uncommented it, which seems to have fixed this particular bug locally, will
have to see if it works in CI.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] [Bug 290] import error caused by soc.decoder.isa.all no longer being generated
From: Jacob Lifshay @ 2020-04-21  4:54 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <bug-290-13-RXl48zu9Pb@https.bugs.libre-soc.org/>

On Mon, Apr 20, 2020, 21:48 <bugzilla-daemon@libre-soc.org> wrote:

> https://bugs.libre-soc.org/show_bug.cgi?id=290
>
> Jacob Lifshay <programmerjake@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|CONFIRMED                   |RESOLVED
>          Resolution|---                         |FIXED
>
> --- Comment #6 from Jacob Lifshay <programmerjake@gmail.com> ---
> (In reply to Luke Kenneth Casson Leighton from comment #5)
> > that was a mistake when i added extra registers
>
> Uncommented it, which seems to have fixed this particular bug locally, will
> have to see if it works in CI.
>

Also fixed another import error where alu_hier was incorrectly imported.

Jacob

>
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 290] import error caused by soc.decoder.isa.all no longer being generated
From: bugzilla-daemon @ 2020-04-21 11:15 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-290-13@https.bugs.libre-soc.org/>

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

--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
excellent.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 12:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #71 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
jean-paul, a quick hack-patch:
https://gitlab.lip6.fr/vlsi-eda/coriolis/-/issues/10

not loading the full views results in losing the offsets during
recursive placement.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 13:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #72 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok i managed to:

* crush doAluFlat.py down to 465x800

* crush doAlu.py down to 520x840

visually you can see that there is plenty of room for improvement,
it is quite fascinating to examine.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 14:32 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #73 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #72)
> ok i managed to:
> 
> * crush doAluFlat.py down to 465x800
> 
> * crush doAlu.py down to 520x840
> 
> visually you can see that there is plenty of room for improvement,
> it is quite fascinating to examine.

Yes. What would be very informative is to try with increasing size
of blocks (16, 32, 64, 128 bits) to see if the "flat" advantage
persists.

I'm pretty sure we can further compress with an optimized manual
routing of the inter-block (especially by using M2+M4 correct
balance for vertical routing)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 15:12 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #74 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #73)
> (In reply to Luke Kenneth Casson Leighton from comment #72)
> > ok i managed to:
> > 
> > * crush doAluFlat.py down to 465x800
> > 
> > * crush doAlu.py down to 520x840
> > 
> > visually you can see that there is plenty of room for improvement,
> > it is quite fascinating to examine.
> 
> Yes. What would be very informative is to try with increasing size
> of blocks (16, 32, 64, 128 bits) to see if the "flat" advantage
> persists.

fascinating. doAlu16.py - worked immediately (after i worked out that
you have to expand the space down the middle to accommodate the extra
tracks, duh)

took about.... 40 seconds to make the code changes: 600.0 width worked
perfectly (good guess, because, later, trying 590 failed).

doAlu16Flat.py - couldn't find a width that would work, not after trying
about 8 times to expand the width.  600 failed.  700 failed with
a missing config (https://gitlab.lip6.fr/vlsi-eda/coriolis/-/issues/11)
800 failed.  900 failed.

> I'm pretty sure we can further compress with an optimized manual
> routing of the inter-block (especially by using M2+M4 correct
> balance for vertical routing)

honestly i think this experiment has worked really well.  the only ways
i would think it worthwhile to expand is in the identification of the
blocks involved in each bit (the muxes).

we do actually need that for another part of the project, because, similarly,
i have some SR Latches which are specified just like the MUXes.

this is a standard recursive graph-walk algorithm, from edges to nodes
to find more (unique, not-previously-seen) edges:

1. here are the starting inputs/outputs
2. what cells are connected to them
3. add their inputs and outputs to a NEW list to recursively search
4. make sure that in the NEW list, the OLD list is excluded from the search
5. repeat from step 2. with the new list

a loop on that algorithm with first [a0, b0, o0] then [a1, b1, o1] etc.
will identify each "group" of cells.

then, it would be good to have a way to specify that only each *group*
should be Etesian-placed, within a manually-created abutment box.

whilst it is by no means perfect (each place a0b0o0, a1b1o1... a15b15o15
could theoretically be in different locations), to identify the cells
algorithmically from the inputs/outputs is much better than to hard-code
what yosys/ABC produces.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 15:22 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #75 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #74)

> this is a standard recursive graph-walk algorithm, from edges to nodes
> to find more (unique, not-previously-seen) edges:
> 
> 1. here are the starting inputs/outputs
> 2. what cells are connected to them
> 3. add their inputs and outputs to a NEW list to recursively search
> 4. make sure that in the NEW list, the OLD list is excluded from the search
> 5. repeat from step 2. with the new list

i will see if i can do this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 15:49 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #76 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
+        if False:
+            print (dir(self.cell))
+            for net in self.cell.getNets():
+                print (net.getName())
+            print (self.cell.getNet("a(0)"))
+            print (dir(self.cell.getNet("a(0)")))
+            for inst in self.cell.getInstances():
+                for net in self.cell.getNets():
+                    if net.getName() == "a(1)":
+                        icell = inst.getMasterCell()
+                        #if len(list(icell.getInstances())) > 0:
+                            #continue # already placed, do not include it
+                        for net in icell.getNets():
+                            print ("inst", icell, "has nets", net.getName())
+            sys.exit(0)
+

i managed to walk the instances pins (of the cell's inputs and outputs,
not what the cell is *connected* to).

hmm...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] Yosys cxxrtl
From: Yehowshua Immanuel @ 2020-04-21 16:02 UTC (permalink / raw)
  To: Libre-RISCV General Development

Whitequark's Yosys Cxx Rtl backend is now merged.

https://twitter.com/whitequark/status/1248427303186493445 <https://twitter.com/whitequark/status/1248427303186493445>

Michael and Luke, you may find it speedier now that the CPU is starting to get more complex.
Especially with OOO and CORDIC.

Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 16:16 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #77 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #76)
> +        if False:
> +            print (dir(self.cell))
> +            for net in self.cell.getNets():
> +                print (net.getName())
> +            print (self.cell.getNet("a(0)"))
> +            print (dir(self.cell.getNet("a(0)")))
> +            for inst in self.cell.getInstances():
> +                for net in self.cell.getNets():
> +                    if net.getName() == "a(1)":
> +                        icell = inst.getMasterCell()
> +                        #if len(list(icell.getInstances())) > 0:
> +                            #continue # already placed, do not include it
> +                        for net in icell.getNets():
> +                            print ("inst", icell, "has nets", net.getName())
> +            sys.exit(0)
> +
> 
> i managed to walk the instances pins (of the cell's inputs and outputs,
> not what the cell is *connected* to).
> 
> hmm...

The concept you are missing here, is the "Plug". A plug is a logical connector
of an instance.

* Plug belongs to Instance. One Plug per external Net.
* Plug may be connected to a Net in the Cell the instance is in
  (method getNet())
* Plug are connected to the Net of the Cell the instance represent,
  called the "master net" (method: getMasterNet()).
* Plug are derived from Components. When a Plug is connected to a Net,
  is put in it's components. So you may find all that is logically
  connected to the Net with net.getPlugs().
* Of courses Instance also have access to all it's Plugs: inst.getPlugs().

So, from the Plug you can know the Net, the Master Net and the instance.
Form the Net you know the Plugs.
From the Instance you can know the PLugs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] Yosys cxxrtl
From: Luke Kenneth Casson Leighton @ 2020-04-21 16:30 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <4EB656C3-8477-40B9-A60A-44579DA58D38@gatech.edu>

On Tue, Apr 21, 2020 at 5:02 PM Yehowshua Immanuel
<yimmanuel3@gatech.edu> wrote:
>
> Whitequark's Yosys Cxx Rtl backend is now merged.
>
> https://twitter.com/whitequark/status/1248427303186493445 <https://twitter.com/whitequark/status/1248427303186493445>

fantastic.

> Michael and Luke, you may find it speedier now that the CPU is starting to get more complex.
> Especially with OOO and CORDIC.

yes.  the last time i turned the (nowhere-near-completed) basic
scoreboard into a BLIF file it was 22 *megabytes*.

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 16:55 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #78 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---

        print (dir(self.cell))
        for net in self.cell.getNets():
            print (net.getName())
        print (self.cell.getNet("a(0)"))
        print (dir(self.cell.getNet("a(0)")))
        net = self.cell.getNet("a(2)")
        print (list(net.getPlugs()))
        for plug in net.getPlugs():
            print (plug, dir(plug))
            components = list(plug.getConnexComponents())
            pc = plug.getCell()
            print ("plug cell", pc)
            mnet = plug.getMasterNet()
            print ("mstnet", mnet)

hmmm this is only printing out add and sub instances
<id:3628 Plug a(2) subckt_48_add.a(2)>
<id:3495 Plug a(2) subckt_49_sub.a(2)>

the reason for that, i am guessing, is because they've been instantiated
(placed).

i need the Plugs that have *not* been instantiated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 17:03 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #79 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
getConnectedPlugs().  maybe.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 17:40 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #80 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #78)
>         print (dir(self.cell))
>         for net in self.cell.getNets():
>             print (net.getName())
>         print (self.cell.getNet("a(0)"))
>         print (dir(self.cell.getNet("a(0)")))
>         net = self.cell.getNet("a(2)")
>         print (list(net.getPlugs()))
>         for plug in net.getPlugs():
>             print (plug, dir(plug))
>             components = list(plug.getConnexComponents())
>             pc = plug.getCell()
>             print ("plug cell", pc)
>             mnet = plug.getMasterNet()
>             print ("mstnet", mnet)
> 
> hmmm this is only printing out add and sub instances
> <id:3628 Plug a(2) subckt_48_add.a(2)>
> <id:3495 Plug a(2) subckt_49_sub.a(2)>
> 
> the reason for that, i am guessing, is because they've been instantiated
> (placed).
> 
> i need the Plugs that have *not* been instantiated.

  Duh? It seems ok to me, according to the netlist of alu16, top level
  "a(2)" is connected only to "add" and "sub". Plug represent logical
  connexions, so they cannot be "placed". The instance they belong to,
  however, may be placed. What Plug connected to "a(2)" do you miss?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* [libre-riscv-dev] [Bug 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-21 18:05 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@https.bugs.libre-soc.org/>

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

--- Comment #81 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #80)

>   Duh? It seems ok to me, according to the netlist of alu16, top level
>   "a(2)" is connected only to "add" and "sub". Plug represent logical
>   connexions, so they cannot be "placed". The instance they belong to,
>   however, may be placed. What Plug connected to "a(2)" do you miss?

tch, tch, you are right.  i needed add_o(2) and sub_o(2).

        find = self.get_net_connections(['add_o(0)', 'sub_o(0)', 'o(0)'],
                                        ['clk', 'rst'])

more ['op', 'abc_829_new_n51', 'op', 'abc_829_new_n51', 'o_next(0)']
set([[0x7fe5b3dd9110<->0x55c7b4b77b10 <id:3433 Instance subckt_0_nmx2_x1
nmx2_x1>], [0x7fe5b3dd9130<->0x55c7b4b92b30 <id:3801 Instance subckt_32_sff1_x4
sff1_x4>]])

at the first level of recursion, it seems to be working.  for a given value of
work.

this will, recursively, grab all unconnected nets that are connected to nets
that are... etc.

however that is too much.

this algorithm can be used to resolve all paths between two points: 
https://www.python.org/doc/essays/graphs/

so by knowing that we want all components involved in add_0(0), sub_o(0)
and o(0) it is possible to find...

hmmm... net "op" is a problem.  if you traverse "op" it goes everywhere.

by excluding "op" as a possibility, i managed to get it to "work"
recursively:

        find = self.get_net_connections(['add_o(1)', 'sub_o(1)', 'o(1)'],
                                        ['clk', 'rst', 'op'])

set([[0x7f13ce86c070<->0x559cb535bc20 <id:3769 Instance subckt_33_sff1_x4
sff1_x4>], [0x7f13ce86c130<->0x559cb535a680 <id:3755 Instance subckt_2_nmx2_x1
nmx2_x1>], [0x7f13ce86c190<->0x559cb5352100 <id:3668 Instance subckt_3_no2_x1
no2_x1>]])

first list is what is wanted (start position), second list is what you do
*not* want.  anything already found will be added recursively to the second
list.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

page:   latest

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git