Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 287] corrections to commit f17100d6c435aec47b17acb188272a7e9b3cf67d
From: bugzilla-daemon @ 2020-04-18  9:17 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-287-13@https.bugs.libre-soc.org/>

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
tobias, see:
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-April/006019.html

-- 
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] morphing 6600 code to use power decoder
From: Luke Kenneth Casson Leighton @ 2020-04-18 11:06 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwxePD_EGrCMrkD9NFMYVeiX8OJ8bzCnPc0zv2Abves5A@mail.gmail.com>

https://libre-soc.org/3d_gpu/multi_bus_arbiter.png

i'm trying to design a multi-bus arbiter which routes:

* multiple banks of src1, src2, src3
* to ANY register-file read-port 1, read-port 2, read-port 3.

at the moment we have:

* multiple banks of src1, src2, src3
* read-port 1 has an INDEPENDENT PriorityPicker to manage access from src1
* read-port 2 has an INDEPENDENT PriorityPicker to manage access from src2
* read-port 3 has an INDEPENDENT PriorityPicker to manage access from src3

the actual arbitration can be done as "select" lines, and, once done,
they can be easily used to enable ORing of data onto buses.

am i overthinking this?

is it as simple as just flattening the multiple banks of src1, src2,
src3 into a linear 1D line of requests?  so if there are 6 banks each
with src1,src2,src3 simply flatten that to 18 requests (for access to
the 3 read-ports)?

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 208] implement CORDIC in a general way sufficient to do transcendentals
From: bugzilla-daemon @ 2020-04-18 21:52 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 #33 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
rats.  i just realised, the dynamic shifting idea isn't going to work.  the
problem is that the atan table value may be small, whilst the x/y large, *or
vice versa*.

so this needs large shifters and complex logic, i dont think its worth it.

-- 
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-04-19  9:51 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>

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

--- Comment #20 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
the other thing, an aspect of the memory hazard and addr matching matrices:

* loads are separated completely from stores
* stores likewise
* atomic memory operations likewise (by marking them as both LD *and* ST)
* the *batch* order is what is preserved
* only one atomic ever gets sent through (batch of QTY 1).
* due to the expansion of the last 4 bits into a bitmap as part of addr_match,
no operations in any one "batch" will have overlapping bytes.  ever.

therefore there is no need - at all - to preserve "order" in any way shape or
form (hence why i said that we do not need a "queue" per se, we need more a L0
Cache/buffer).

(this wording - L0 cache/buffer - came out of the discussion on comp.arch with
Ivan. 8 entries is likely to be sufficient for us)

to emphasise:

* *at no time* will the DMs put out a mixed batch of LDs, STs or Atomics.
* acknowledging, clearing and completing each batch before moving onto the next
is absolutely critical.
* except for IO and Atomics (which will only be sent down one at a time anyway)
the order of LDs (or STs) can be entirely arbitrary.

also we can get away with full IO memory order preservation by treating them as
"Atomic".  this will result in them only being sent one at a time, in strict
order.

if the exact same dependency system were used at the L2 layer we could do full
SMP TSO with no difficulty.

-- 
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-04-19  9:57 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>

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

--- Comment #21 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #19)
> (In reply to Luke Kenneth Casson Leighton from comment #18)

> > ok so those 1 MB texture buffers you mentioned before are accessed multiple
> > times in near-succession?
> 
> Yes. Though several different textures can be accessed in an interleaved
> fashion.

ok that's fine.

so what will happen, because the addr match is on the last 4k (11 bits),
anything that has on the same 4k LSBs even though the MSBs do not match, gets
delayed a couple of cycles and, after the false positive clears through the
memory system, the "not-actually-conflicting" LDST's turn will come next.

Mitch's analysis showed that in practice this is such a rare occurrence that
the penalty is not worth being concerned about.

-- 
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-04-19 15:22 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>

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

--- Comment #22 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://libre-soc.org/3d_gpu/architecture/6600scoreboard/

i just updated this page, a new section "L0 Cache/Buffer".  it contains a
diagram i did a couple weeks ago:

https://libre-soc.org/3d_gpu/architecture/6600scoreboard/600x-mem_l0_to_l1_bridge.png

the actual algorithm is incredibly simple:

* priority picker picks one (and only one) address (per L0 cache/buffer)
* for all rows greater than the one picked, match against all MSBs of
  the address, bits 5 and above.
* all matching rows, OR the 16-bit bitmap representing {LSBs 0-3 plus
LD/ST-len} 

those ORed bitmaps become the "byte read/write-enable" lines on a given
L1 cache line.

that's it - that's all there is to it.

the "complex" bit is the N-in/out multiplexing from 16-in on the 8 LD/ST
FunctionUnits (2 ports per FU because 1 is for "normal" requests and the
2nd is for misaligned addresses)

however i just realised that if we can accept an increase in size of the L0
cache/buffer from 8 to 16 entries - or to limit the number of LD/ST Function
Units to 6 - then we can instead simply have one *dedicated* "entry" for
each and every FU, and the entire MASSIVE 16-to-4 multiplexer completely
disappears.

i'll draw it out.

the caveat: we now have a 16-entry (or 12-entry) L0 Cache/Buffer, which
unfortunately requires up to a 16-way CAM on the *ENTIRE* address from
bits 5 and upwards.

it *might* be possible to inherit (yet again) from the addr_match.py classes,
which already has a full triangular comparison of all-against-all in 
bits 4 thru 11.

-- 
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-04-19 17:46 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>

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

--- Comment #23 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
https://libre-soc.org/3d_gpu/mem_l0_to_l1_bridge_v2.png

ok done. it works like this:

* each FU (0-7) produces 2 LD/ST addresses which are broken up like this:

  addr1[0..3] addr1[4] addr1[5..11] addr1[12..48]
  addr2[0..3] addr2[4] addr2[5..11] addr2[12..48]

  where the relationship between addr1 and addr2 is:

       addr1[5..11] + 1 == addr2[5..11]

* addr1[0..3], in combination with the LD/ST len (1/2/3/4) is turned into
  a bytemap mask, 24 bits in length.  this bytemask is broken down into
  two halves:

      bytemask1, bytemask2 = map_addr(addr, LDST_len) [0..15], [16..23]

  i.e. anything that does not fit fully into bytemask1 is a "misaligned"
  LD/ST and the remainder overflows into bytemask2.

* if addr[4..11] == 0b111111111 and bytemask2 is non-zero, this indicates
  a "misaligned major page fault".

   this is a situation that we are *not* going to deal with (and it has
   been catered for in the 3.0B spec)

* all 16 FU LD/ST re-encodings of the (addr, LDST_len) are lined up in a
  table.  this table breaks down, alternating between:

  * FU # aligned     or FU # misaligned
  * addr1[5:11]      or addr2[5:11]
  * addr[12:48] for *BOTH*
  * bytemap1[0:15]   or bytemap2[0:15]
  * data1[0:15]      or data2[15]

note that addr[4] is *not* included in this because it is used to select
whether L1 cache bank #0 or #1 is to be used.

the algorithm for merging of LD/STs into *one single L1 cache line* is:

1). With a PriorityPicker find the index (row) of the first valid LD/ST request

2). For all entries after that row, compare Addr[5:11] and Addr[12:48].

3). If "match" on both, OR the byte-mask for that row onto the output.

that's it.  that's really all there is to it.


one thing that's important to note: there are only actually *eight* comparisons
of addr[12:48] needed (not 16), because the addr[12:48] is *identical* for
every *pair* of rows.

that however is still *seven* potential 36-bit CAM hits (seven lots of 36-bit
XOR gates).  which is a hell of a lot.

if we could somehow use the L1 "tag" in place of Addr[12:48], that would save a
huge amount of power.  unfortunately, every way i can think of that would get
the tag *into* L0 is either equally power-consuming, or results in multi-cycle
latency.

if we could reliably use a hash instead, i would suggest it.  however,
unfortunately, the risk of a collision is too detrimental consequences.

the "sensible" option that does not have too detrimental an effect on
performance is: reduce the number of LD/ST FUs to 6.  that would result in only
12 rows.

-- 
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 288] New: intro post for powerpc-notebook.org and https://www.powerprogress.org/en/
From: bugzilla-daemon @ 2020-04-19 19:29 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 288
           Summary: intro post for powerpc-notebook.org and
                    https://www.powerprogress.org/en/
           Product: Libre-RISC-V Website
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

Roberto from PowerPC-notebook and PowerProgress Community says:

"Regarding starting with cross links in our websites to our projects, from our
side  we can start with a short post that can  intro https://libre-soc.org/
project.  if you and your team will provide a short text I will publish next
days."

what would we like to have on the news page of powerprogress.org?

and, what should we put on libre-soc?

-- 
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 289] New: LD/ST Function Unit address match "vector" optimisation
From: bugzilla-daemon @ 2020-04-20  9:10 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 289
           Summary: LD/ST Function Unit address match "vector"
                    optimisation
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

at the L0 Cache/Buffer level, and in the address-match matrix, a massive
array of XOR gates (comparators) is needed.  this is a huge power drain.

however back at the vector-issue phase, information is known between
multiple units: there is a very high probability that related element
addresses will not have changed (especially on element-strided
LD/STs) and, furthermore, it is very easy to detect.

https://groups.google.com/d/msg/comp.arch/cbGAlcCjiZE/IDhmQPS6AAAJ

therefore as an enhancement, when Vector LD/STs are involved, provide
additional information down to the address-match and L0 cache/buffer
that saves huge amounts of power.

-- 
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 289] LD/ST Function Unit address match "vector" optimisation
From: bugzilla-daemon @ 2020-04-20  9:10 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-289-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=216

-- 
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 216] LOAD STORE buffer needed
From: bugzilla-daemon @ 2020-04-20  9:10 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-216-13@https.bugs.libre-soc.org/>

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

Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.libre-soc.org/
                   |                            |show_bug.cgi?id=289

-- 
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 14: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 #57 from Jean-Paul.Chaput@lip6.fr ---

Hello Jock & Luke,

I just commited in Coriolis & soclayout my latest corrections and
enhancements. You will find under experiment7/Status.rst
detailed comments about what I have done and the remaining
questions.

Good reading and best regards,

-- 
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 15: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 #58 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #57)
> Hello Jock & Luke,
> 
> I just commited in Coriolis & soclayout my latest corrections and
> enhancements. You will find under experiment7/Status.rst
> detailed comments about what I have done and the remaining
> questions.

appreciated.

hmm is everything committed? i just git pulled up to here:

commit 8978074fe72acb90b94a6c3b20ba820a1b753b69
Author: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
Date:   Mon Apr 20 12:53:07 2020 +0200

and for alliance-check-toolkit:
commit b9e5d37953b423b2a17c0599289d0682447c5f35
Author: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
Date:   Fri Apr 10 12:26:15 2020 +0200

the reason i ask is because after rebuilding coriolis2 i get this:

Traceback (most recent call last):
  File "doAlu16Flat.py", line 137, in <module>
    success = scriptMain(**kwargs)
  File "doAlu16Flat.py", line 132, in scriptMain
    return alu16.build()
  File "doAlu16Flat.py", line 89, in build
    result = self.route()
  File "/home/lkcl/soclayout/experiments7/utils.py", line 191, in route
    katana.loadGlobalRouting(Anabatic.EngineLoadGrByNet)
hurricane.HurricaneError: [BUG] Unmanaged Configuration [16843266] =
[2+2+0+1,1+0] <id:1492 Net "a(5)" e-- LOGICAL i--- (IN)> in <id:5325
Anabatic::GCell <Box 200l 0l 250l 50l> ----------M---,i-A- 15>
      The global routing seems to be defective.

-- 
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 17:15 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 #59 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #58)
> (In reply to Jean-Paul.Chaput from comment #57)
>   File "doAlu16Flat.py", line 89, in build
>     result = self.route()
>   File "/home/lkcl/soclayout/experiments7/utils.py", line 191, in route
>     katana.loadGlobalRouting(Anabatic.EngineLoadGrByNet)
> hurricane.HurricaneError: [BUG] Unmanaged Configuration [16843266] =
> [2+2+0+1,1+0] <id:1492 Net "a(5)" e-- LOGICAL i--- (IN)> in <id:5325
> Anabatic::GCell <Box 200l 0l 250l 50l> ----------M---,i-A- 15>
>       The global routing seems to be defective.

Argh! Yes everything was commited. But, as we are not 100% clone of
each other (what Intel would call "copy exact" for its foundries),
you may have got a slighty different Yosys netlist and so a
slightky different placement. I was lazy, I didn't manage that case.
I will do it this evening...

-- 
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 18:10 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 #60 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jean-Paul.Chaput from comment #59)
> (In reply to Luke Kenneth Casson Leighton from comment #58)
> > (In reply to Jean-Paul.Chaput from comment #57)
> >   File "doAlu16Flat.py", line 89, in build
> >     result = self.route()
> >   File "/home/lkcl/soclayout/experiments7/utils.py", line 191, in route
> >     katana.loadGlobalRouting(Anabatic.EngineLoadGrByNet)
> > hurricane.HurricaneError: [BUG] Unmanaged Configuration [16843266] =
> > [2+2+0+1,1+0] <id:1492 Net "a(5)" e-- LOGICAL i--- (IN)> in <id:5325
> > Anabatic::GCell <Box 200l 0l 250l 50l> ----------M---,i-A- 15>
> >       The global routing seems to be defective.
> 
> Argh! Yes everything was commited. But, as we are not 100% clone of
> each other (what Intel would call "copy exact" for its foundries),
> you may have got a slighty different Yosys netlist and so a
> slightly different placement. 

iinteresting.  i remember your warning about that on bug #178.

ahh so in case you need to repro that:

$ cd ~/yosys
$ git diff
diff --git a/Makefile b/Makefile
index e9dfd9df..8a935579 100644
--- a/Makefile
+++ b/Makefile
@@ -128,7 +128,7 @@ bumpversion:
 # is just a symlink to your actual ABC working directory, as 'make mrproper'
 # will remove the 'abc' directory and you do not want to accidentally
 # delete your work on ABC..
-ABCREV = 71f2b40
+ABCREV = default
 ABCPULL = 1
 ABCURL ?= https://github.com/berkeley-abc/abc

> I was lazy, I didn't manage that case.
> I will do it this evening...

i'll git pull on yosys and recompile.

commit ae115fa3aac9acf7534b3f7c08afaa1b86bfc4ad
Merge: 2b1fb8c0 35990b95
Author: Claire Wolf <clifford@clifford.at>
Date:   Mon Apr 20 14:51:40 2020 +0200

-- 
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 18:25 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 #61 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
wark.  nope :)

hurricane.HurricaneError: [BUG] Unmanaged Configuration [16843266] =
[2+2+0+1,1+0] <id:1492 Net "a(5)" e-- LOGICAL i--- (IN)> in <id:5325
Anabatic::GCell <Box 200l 0l 250l 50l> ----------M---,i-A- 14>
      The global routing seems to be defective.

-- 
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 18:33 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 #62 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
this is a new one, too:

$ make clean
$ make vst
$ python doAlu16.py

        <event:00000659 0:917.91:52l> &<id:4837 Vertical o(11) METAL3 [125l
535l] [125l 585l] 2l rpD:2 -----CG-----w-----bb- [534l:586l] 52l 0------>
        <event:00000660 0:662.935:47l> &<id:4806 Vertical o(2) METAL3 [125l
90l] [125l 135l] 2l rpD:2 -----CG-----w-----bb- [89l:136l] 47l 0------>
        <event:00000661 0:662.935:12l> &<id:4846 Vertical o(4) METAL3 [125l
190l] [125l 200l] 2l rpD:2 -----CG-----w-----bb- [189l:201l] 12l 0------>
        <event:00000662 0:662.935:7l> &<id:4869 Vertical o(10) METAL3 [125l
495l] [125l 500l] 2l rpD:2 -----CG-----w-----bb- [494l:501l] 7l 0------>
     o  Repair Stage.
        <repair.queue:00000000>
  o  Computing statistics.
     - Processeds Events Total .............................................
663
     - Unique Events Total .................................................
572
     - # of GCells ..........................................................
64
     - Track Segment Completion Ratio ............................. 100%
[572+0]
     - Wire Length Completion Ratio ............................. 100%
[11039+0]
     - Wire Length Expand Ratio ............................. -1.02%
[min:11153]
     - Unrouted horizontals .......................................... -nan%
[0]
     - Unrouted verticals ............................................ -nan%
[0]
     - Done in ................................................. 0.03s,
413696Kb
     - Raw measurements .............................. 0.030762s,
+404Kb/287.8Mb
  o  Checking Katana Database coherency.
[STOP] After routing <id:119 Cell add>
       Type <y> to continue, <n> to abort: (y) 

(y here)

  File "/home/lkcl/soclayout/experiments7/utils.py", line 193, in route
    katana.runNegociate(Katana.Flags.NoFlags)
hurricane.HurricaneError: [ERROR] NegociateWindow::createTrackSegment(): No
track near axis of <id:9171 Vertical b(5) METAL3 [-1l 275l] [-1l 275l] 2l
rpD:15 -----C-------AS-il--->.

-- 
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 19:00 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 #63 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Jean-Paul.Chaput from comment #59)
> (In reply to Luke Kenneth Casson Leighton from comment #58)
> > (In reply to Jean-Paul.Chaput from comment #57)
> >   File "doAlu16Flat.py", line 89, in build
> >     result = self.route()
> >   File "/home/lkcl/soclayout/experiments7/utils.py", line 191, in route
> >     katana.loadGlobalRouting(Anabatic.EngineLoadGrByNet)
> > hurricane.HurricaneError: [BUG] Unmanaged Configuration [16843266] =
> > [2+2+0+1,1+0] <id:1492 Net "a(5)" e-- LOGICAL i--- (IN)> in <id:5325
> > Anabatic::GCell <Box 200l 0l 250l 50l> ----------M---,i-A- 15>
> >       The global routing seems to be defective.
> 
> Argh! Yes everything was commited. But, as we are not 100% clone of
> each other (what Intel would call "copy exact" for its foundries),
> you may have got a slighty different Yosys netlist and so a
> slightky different placement. I was lazy, I didn't manage that case.
> I will do it this evening...

  This should be corrected by the last commit.

-- 
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 19:08 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 #64 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #62)
> this is a new one, too:
> 
> $ make clean
> $ make vst
> $ python doAlu16.py
> 
>         <event:00000659 0:917.91:52l> &<id:4837 Vertical o(11) METAL3 [125l
> 535l] [125l 585l] 2l rpD:2 -----CG-----w-----bb- [534l:586l] 52l 0------>
>         <event:00000660 0:662.935:47l> &<id:4806 Vertical o(2) METAL3 [125l
> 90l] [125l 135l] 2l rpD:2 -----CG-----w-----bb- [89l:136l] 47l 0------>
>         <event:00000661 0:662.935:12l> &<id:4846 Vertical o(4) METAL3 [125l
> 190l] [125l 200l] 2l rpD:2 -----CG-----w-----bb- [189l:201l] 12l 0------>
>         <event:00000662 0:662.935:7l> &<id:4869 Vertical o(10) METAL3 [125l
> 495l] [125l 500l] 2l rpD:2 -----CG-----w-----bb- [494l:501l] 7l 0------>
>      o  Repair Stage.
>         <repair.queue:00000000>
>   o  Computing statistics.
>      - Processeds Events Total .............................................
> 663
>      - Unique Events Total .................................................
> 572
>      - # of GCells
> .......................................................... 64
>      - Track Segment Completion Ratio ............................. 100%
> [572+0]
>      - Wire Length Completion Ratio ............................. 100%
> [11039+0]
>      - Wire Length Expand Ratio ............................. -1.02%
> [min:11153]
>      - Unrouted horizontals .......................................... -nan%
> [0]
>      - Unrouted verticals ............................................ -nan%
> [0]
>      - Done in ................................................. 0.03s,
> 413696Kb
>      - Raw measurements .............................. 0.030762s,
> +404Kb/287.8Mb
>   o  Checking Katana Database coherency.
> [STOP] After routing <id:119 Cell add>
>        Type <y> to continue, <n> to abort: (y) 
> 
> (y here)
> 
>   File "/home/lkcl/soclayout/experiments7/utils.py", line 193, in route
>     katana.runNegociate(Katana.Flags.NoFlags)
> hurricane.HurricaneError: [ERROR] NegociateWindow::createTrackSegment(): No
> track near axis of <id:9171 Vertical b(5) METAL3 [-1l 275l] [-1l 275l] 2l
> rpD:15 -----C-------AS-il--->.

  I was hoping it will not show... The current workaround is to slightly
enlarge
  the block abutment box, 10 lambdas by 10 lambdas.

-- 
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 19: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 #65 from Jean-Paul.Chaput@lip6.fr ---
(In reply to Luke Kenneth Casson Leighton from comment #60)
> (In reply to Jean-Paul.Chaput from comment #59)
> > (In reply to Luke Kenneth Casson Leighton from comment #58)
> > > (In reply to Jean-Paul.Chaput from comment #57)
> > >   File "doAlu16Flat.py", line 89, in build
> > >     result = self.route()
> > >   File "/home/lkcl/soclayout/experiments7/utils.py", line 191, in route
> > >     katana.loadGlobalRouting(Anabatic.EngineLoadGrByNet)
> > > hurricane.HurricaneError: [BUG] Unmanaged Configuration [16843266] =
> > > [2+2+0+1,1+0] <id:1492 Net "a(5)" e-- LOGICAL i--- (IN)> in <id:5325
> > > Anabatic::GCell <Box 200l 0l 250l 50l> ----------M---,i-A- 15>
> > >       The global routing seems to be defective.
> > 
> > Argh! Yes everything was commited. But, as we are not 100% clone of
> > each other (what Intel would call "copy exact" for its foundries),
> > you may have got a slighty different Yosys netlist and so a
> > slightly different placement. 
> 
> iinteresting.  i remember your warning about that on bug #178.
> 
> ahh so in case you need to repro that:
> 
> $ cd ~/yosys
> $ git diff
> diff --git a/Makefile b/Makefile
> index e9dfd9df..8a935579 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -128,7 +128,7 @@ bumpversion:
>  # is just a symlink to your actual ABC working directory, as 'make mrproper'
>  # will remove the 'abc' directory and you do not want to accidentally
>  # delete your work on ABC..
> -ABCREV = 71f2b40
> +ABCREV = default
>  ABCPULL = 1
>  ABCURL ?= https://github.com/berkeley-abc/abc
> 
> > I was lazy, I didn't manage that case.
> > I will do it this evening...
> 
> i'll git pull on yosys and recompile.
> 
> commit ae115fa3aac9acf7534b3f7c08afaa1b86bfc4ad
> Merge: 2b1fb8c0 35990b95
> Author: Claire Wolf <clifford@clifford.at>
> Date:   Mon Apr 20 14:51:40 2020 +0200

I think this is a more wider issue. Throughout all the project, all the
versions
of the tools should be fixed, and when bumped everybody should do it at the
same
time. And when the chip is finished, a full snapshot of all the versions should
be packed alongside the chip source code.

This is the way we did it at LIP6.

-- 
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 19:20 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

Jacob Lifshay <programmerjake@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |programmerjake@gmail.com

--- Comment #66 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Jean-Paul.Chaput from comment #65)
> I think this is a more wider issue. Throughout all the project, all the
> versions
> of the tools should be fixed, and when bumped everybody should do it at the
> same
> time. And when the chip is finished, a full snapshot of all the versions
> should
> be packed alongside the chip source code.

Sounds like we should use git submodules!

-- 
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 19:52 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 #67 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #66)

> Sounds like we should use git submodules!

with each of the build dependencies with their specific versions
added, yeah.

-- 
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 20:45 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 #68 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
how come i manage to break things all the time??
https://gitlab.lip6.fr/vlsi-eda/coriolis/-/issues/9
:)

-- 
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 21:00 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 #69 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
mooooo
https://gitlab.lip6.fr/vlsi-eda/alliance/-/issues/1

placement (just visual i hope) has the positioning ignored under
certain circumstances.  it is very weird.

-- 
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 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

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