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-13 14:35 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 #3 from Michael Nolan <mtnolan2640@gmail.com> ---
I was able to translate the linked myhdl code to nmigen and implement both a
state machine based and pipelined cordic here:
https://git.libre-soc.org/?p=ieee754fpu.git;a=tree;f=src/ieee754/cordic;h=3f06900baa42651410d661739fb616e4b3020c52;hb=77f150cff440bed025e2487b6f0fcda9f529290b

You can configure the width, as well as the number of cordic rounds per
pipeline stage. There are some accuracy issues with it though - it exactly
matches the behavior of the myhdl one, but the results it gives can be off by
1% or so from that obtained using sin() or cos() on 16 bit numbers.

-- 
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-13 17:23 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 #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #3)
> I was able to translate the linked myhdl code to nmigen and implement both a
> state machine based and pipelined cordic here:
> https://git.libre-soc.org/?p=ieee754fpu.git;a=tree;f=src/ieee754/cordic;
> h=3f06900baa42651410d661739fb616e4b3020c52;
> hb=77f150cff440bed025e2487b6f0fcda9f529290b

cool!  well that was easy :)

> You can configure the width, as well as the number of cordic rounds per
> pipeline stage. There are some accuracy issues with it though - it exactly
> matches the behavior of the myhdl one, but the results it gives can be off
> by 1% or so from that obtained using sin() or cos() on 16 bit numbers.

yes.  i believe it's well-known that to get 16-bit accuracy you need
32-bit registers.

i made a couple of corrections btw - frickin well done for working out
the pipeline API with zero assistance - that's deeply impressive given
that, other than the docstring comments, there's no "documentation" on
it.

CordicInitialData needed to "yield self.z0" (not self.z)

"yield from" is reserved for a way to yield *from* something that is
itself iteratable (such as another function).  self.z0 is in fact
iterable, so what would be returned by "yield from" would be first
self.z0[0], then on the next iteration self.z0[1] and so on which
would be very painful.

"yield" just returns "that object".

however... we have a bit of a problem back in nmutil.iocontrol NextControl
and PrevControl iteration, in that it can't actually properly work out
if the *object* that you are iterating should be yielded or yielded *from*.
so i added a hack "check if data has a ports function".

however i've just right now worked out that we could detect if the object
is iterable with isinstance(self.data_o, Iterable).
so that's just been committed.

i also added an rtlil test because i was fascinated to see what the
graphviz looks like.


--- a/src/ieee754/cordic/pipe_data.py
+++ b/src/ieee754/cordic/pipe_data.py
@@ -10,11 +10,14 @@ class CordicInitialData:
         self.z0 = Signal(range(-ZMAX, ZMAX), name="z")     # denormed result

     def __iter__(self):
-        yield from self.z
+        yield self.z0

     def eq(self, i):
         return [self.z0.eq(i.z0)]

 class CordicData:

@@ -27,9 +30,12 @@ class CordicData:
         self.z = Signal(range(-ZMAX, ZMAX), name="z")     # denormed result

     def __iter__(self):
-        yield from self.x
-        yield from self.y
-        yield from self.z
+        yield self.x
+        yield self.y
+        yield self.z

     def eq(self, i):
         ret = [self.z.eq(i.z), self.x.eq(i.x), self.y.eq(i.y)]
diff --git a/src/ieee754/cordic/test/test_pipe.py
b/src/ieee754/cordic/test/test_pipe.py
index 880351a..b7eaf8a 100644
--- a/src/ieee754/cordic/test/test_pipe.py
+++ b/src/ieee754/cordic/test/test_pipe.py
@@ -1,6 +1,7 @@
 from nmigen import Module, Signal
 from nmigen.back.pysim import Simulator, Passive
 from nmigen.test.utils import FHDLTestCase
+from nmigen.cli import rtlil

 from ieee754.cordic.sin_cos_pipeline import CordicBasePipe
 from ieee754.cordic.pipe_data import CordicPipeSpec
@@ -16,6 +17,13 @@ class SinCosTestCase(FHDLTestCase):
         pspec = CordicPipeSpec(fracbits=fracbits, rounds_per_stage=4)
         m.submodules.dut = dut = CordicBasePipe(pspec)

+        for port in dut.ports():
+            print ("port", port)
+
+        vl = rtlil.convert(dut, ports=dut.ports())
+        with open("test_cordic_pipe_sin_cos.il", "w") as f:
+            f.write(vl)
+
         z = Signal(dut.p.data_i.z0.shape())
         z_valid = Signal()
         ready = Signal()
(END)

-- 
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-13 17:34 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 #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok so would you like to do the next step? which is, yep you guessed it:
IEEE754 FP sin and cos :)

i think... from doing some reading (last year) i have a vague recollection
that you have to be careful with the smaller ranges at one end, thus
only using a 45 degree range (+/-) and subtracting and adding accordingly
in order to compute an intermediary result, followed by adjustment
(add/subtract to/from fractions of pi).

if you naively try to do from 0-90 then at one end (i forget which) because
sin/cos is flat at one end, something to do with the atan2 tables getting
very small, you end up with inaccuracies creeping in and stacking up
rapidly.

-- 
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: whygee @ 2020-04-13 17:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDy3aNGSVRUd-=hRC8b-Dt-7FPbi2q-=rRxoh_7=8W3_qg@mail.gmail.com>

On 2020-04-13 16:16, Luke Kenneth Casson Leighton wrote:
> https://groups.google.com/forum/#!topic/comp.arch/qeMsE7UxvlI
> https://libre-soc.org/3d_gpu/architecture/6600scoreboard/
> https://www.youtube.com/watch?v=ohHbWRLDCfs
> 
> this is quite a significant core change to the 6600 scoreboard engine,
> so i'm soliciting outside help in reviewing it.  ironically (and very
> much to the point) i realised an error towards the end of the
> description.

I couldn't be sure to understand all the subtleties.

However remove the comment from "Tom"/Temar
who is a click-harvesting bot on youtube.

Anyway : impressive work !

> l.
yg

_______________________________________________
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-13 18:27 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <3e3c538da863fba6572ac948469c763c@f-cpu.org>

On Mon, Apr 13, 2020 at 6:46 PM <whygee@f-cpu.org> wrote:
>
> On 2020-04-13 16:16, Luke Kenneth Casson Leighton wrote:
> > https://groups.google.com/forum/#!topic/comp.arch/qeMsE7UxvlI
> > https://libre-soc.org/3d_gpu/architecture/6600scoreboard/
> > https://www.youtube.com/watch?v=ohHbWRLDCfs
> >
> > this is quite a significant core change to the 6600 scoreboard engine,
> > so i'm soliciting outside help in reviewing it.  ironically (and very
> > much to the point) i realised an error towards the end of the
> > description.
>
> I couldn't be sure to understand all the subtleties.

CompUnits are a forward-progress looped Finite-State-Machine.  Issue,
Read, Write, Issue, Read, Write.  that's now Issue, {Read1/2/3},
{Write1/2}, Issue {Read1/2/3}, {Write1/2} repeat repeat.

Dependency Matrices: Reads stop Writes, Writes stop Reads.  now there
are multiple read-regs, any one of those multiple Read-Regs must stop
Writes, any one of those multiple Write-Regs must stop Reads.

> However remove the comment from "Tom"/Temar
> who is a click-harvesting bot on youtube.

done.

> Anyway : impressive work !

appreciated.  now i have to implement it.  and modify all the
dependent code that uses it.  sigh.  it'll be about a month's work.

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 284] New: TypeError Object is not an nMigen signal
From: bugzilla-daemon @ 2020-04-14  8:26 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 284
           Summary: TypeError Object is not an nMigen signal
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: Other
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Source Code
          Assignee: lkcl@lkcl.net
          Reporter: libre-soc@platen-software.de
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

When running tests with the latest version of nmigen I get the following error:

Traceback (most recent call last):
  File "test_sim.py", line 98, in test_sub
    self.run_tst_program(program, [1, 2, 3, 4, 5])
  File "test_sim.py", line 102, in run_tst_program
    self.run_tst(prog, simulator)
  File "test_sim.py", line 49, in run_tst
    traces=pdecode2.ports()):
  File
"/usr/local/lib/python3.7/dist-packages/nmigen-0.3.dev20+g0e40dc0-py3.7.egg/nmigen/back/pysim.py",
line 1125, in write_vcd
    vcd_file=vcd_file, gtkw_file=gtkw_file, traces=traces)
  File
"/usr/local/lib/python3.7/dist-packages/nmigen-0.3.dev20+g0e40dc0-py3.7.egg/nmigen/back/pysim.py",
line 95, in __init__
    if trace not in signal_names:
  File "/usr/lib/python3.7/_collections_abc.py", line 666, in __contains__
    self[key]
  File
"/usr/local/lib/python3.7/dist-packages/nmigen-0.3.dev20+g0e40dc0-py3.7.egg/nmigen/hdl/ast.py",
line 1392, in __getitem__
    key = None if key is None else self._map_key(key)
  File
"/usr/local/lib/python3.7/dist-packages/nmigen-0.3.dev20+g0e40dc0-py3.7.egg/nmigen/hdl/ast.py",
line 1582, in __init__
    raise TypeError("Object {!r} is not an nMigen signal".format(signal))
TypeError: Object (rec <unnamed> rego rego_ok) is not an nMigen signal

I already fixed that kind of error and it reappeared after running git pull.

-- 
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 284] TypeError Object is not an nMigen signal
From: bugzilla-daemon @ 2020-04-14  8:38 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-284-13@https.bugs.libre-soc.org/>

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

Jacob Lifshay <programmerjake@gmail.com> changed:

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

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
which nmigen remote are you using?
also, which repo is this? soc?

You could try looking through the recent builds on salsa to see if the error is
reproduced there:
https://salsa.debian.org/Kazan-team/soc/pipelines

-- 
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 284] TypeError Object is not an nMigen signal
From: bugzilla-daemon @ 2020-04-14 11:09 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-284-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Tobias Platen <libre-soc@platen-software.de> ---
I am using the https://github.com/nmigen/nmigen repo,
but our documentation says https://github.com/m-labs/nmigen

I am using the soc repo and the Kazan-team pipeline has failed too.
https://salsa.debian.org/Kazan-team/soc/pipelines/125651/failures.

The error is a different one in this case:
ModuleNotFoundError (No module named 'alu_hier')

-- 
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 284] TypeError Object is not an nMigen signal
From: bugzilla-daemon @ 2020-04-14 11:37 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-284-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Tobias Platen from comment #2)
> I am using the https://github.com/nmigen/nmigen repo,
> but our documentation says https://github.com/m-labs/nmigen

please do update the documentation - don't wait, just do it
(and send a message to the list saying that it's been done).

> I am using the soc repo and the Kazan-team pipeline has failed too.
> https://salsa.debian.org/Kazan-team/soc/pipelines/125651/failures.

when those messages are available in a resource controlled by us - not
by debian, not by the proprietary hosting company gitlab - and replicable
by anyone, without requiring a permanent internet connection - i'll take a
look at them.

(reminds me, we really must do something about making bugzilla available
offline)

> The error is a different one in this case:
> ModuleNotFoundError (No module named 'alu_hier')

i'm dealing with some augmentations and changes to the 6600 scoreboard,
which is a particularly complex area.

-- 
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 285] New: bugzilla to be made available "offline"
From: bugzilla-daemon @ 2020-04-14 11:48 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 285
           Summary: bugzilla to be made available "offline"
           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: ---

one of the important aspects of this project is it being possible to
replicate (for both offline real-time collaboration as well as legacy
archiving purposes) all resources.

bugzilla is one major piece of critical functionality that is also a
critical online resource.

about the only offline bugtracker that exists (and is any good) is
bugseverywhere.

that's interesting.
https://github.com/kalkin/be/blob/master/interfaces/email/interactive/be-handle-mail

-- 
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 286] New: DataPointer concept: long-immediate references
From: bugzilla-daemon @ 2020-04-14 17:02 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 286
           Summary: DataPointer concept: long-immediate references
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Specification
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

original discussion at:
https://groups.google.com/d/msg/comp.arch/DeGUdZhh1Jc/LzRc61JSAQAJ


i raised an alternative idea last year: a Data Pointer.  similar to a
Program Counter and/or Stack Pointer, the Data Pointer is incremented
implicitly by each operation requiring an immediate, and, in extreme
versions, that may be incremented *bit-wise* rather than on byte, word
or dword boundaries.

opcodes requiring immediates then specify the number of *bits* they wish to
use. the Data Pointer automatically increments such that the next instruction
loads from the subsequent memory address, not the same one.

as an off-the-wall concept, i never thought through how you would actually
*set* the Data Pointer in the first place, nor how loops would be dealt with.

L1-cacheing of the constants (and reading them and including them in the
I-stream) is not a big deal.  however separating them from actual instructions
does actually become a bit of a bind.  perhaps the D-cache could be used
(treat them as data).

loops are the biggest bugbear.  however an idea just occurred to me.
with only a few bits being needed to specify how *much* of the memory pointed
to by the Data Pointer is to be used as an immediate, the remaining (spare)
bits can be taken as an offset by which the Data Pointer is to be "wound back"
(or forward).

perhaps even some mode-bits could be used to indicate, "New Data Pointer Starts
Here and there is a block of immediates of size NN following this instruction":

addi R0, R1, {dpencoding}

dpencoding:

11 10 9 8 7    | 7 6        | 5 4 3 2 1 0  |
immblocklen x4 | immbytelen | immjump x4   |

something like that.

* immblocklen x 32 is the space reserved following this instruction,
  to which the Data Pointer is to be immediately set (zero indicates
  "no change").  thus the PC *knows* that it must add 4ximmblocklen
  bytes to the PC
* immbytelen - the length (in bytes? maybe bits?) of the immediate,
  0b000=8, 0b001=16 etc. etc.  after the immediate is read (immediately)
  from the DataPointer address, the DataPointer must be incremented
  by this amount, only if immjump == 0
* immjump - a signed number of words that (rounded) the DataPointer
  must "jump" by (forward or backwards) *INSTEAD* of incrementing
  by immbytelen.

that should probably do the trick for a first iteration.

analysis:

* compared to standard immediate-loading: for small immediates it's not
  as nice because you have to use the 12-bit immediate space as a pointer
  therefore, simple solution to that: only use this for long immediates,
  or, use 1 extra bit to indicate "11-bit immediate or DataPointer"
  encoding

* with no "construction" of long immediates using 32-bit stuff, it's
  definitely much more compact.


variants include that immjump is *always* set, and is always relative
to DataPointer.  this would actually be better because if we assume
that when the DP is set (immblocklen != 0) that instruction wants
the *first* item @DP, we no longer need both immblocklen and immjump:

7    | 6 5 4 3 2       | 1 0    |
mode | DPlen_or_DPoffs | immlen |

* mode == 0: DPlen x 4 bytes of "offsets" follow this instruction.
             - set DP = PC + 4
             - assume DPoffs = 0.
             - immed = @[DP] of length immlen (bytes? words?
             - add DPlen x 4 to PC

* mode == 1: DPoffs is in bytes 6:2.
             - PC increments as normal (+4)
             - DP does *NOT CHANGE*
             - immed = @[DP + DPoffs*4] of length immlen (bytes? words?)

this gives relatively few bits, and it would not be unreasonable to snarf
a few bits out of a "normal" 12-bit immediate range:

12 11 10 9 8 |   7 6 5 4 3 2 1 0
1  1   1 1 1 | { dpencoding }
N  N   N N N     N N N N N N N N - "normal" immediate


the only complexity would be compiler-side creation of tables that initialise
correctly and in reasonable proximity.

also you'd either lose one main register (one as normal SP, one now as DP)
or it would be required to add a special register (CSR), plus context-saving
to ensure it's not corrupted during interrupts.

l.




assume the 2nd scheme in the latter part of what i wrote (absolute-addressed
DataPointer rather than the incremental-version):

# some prior code which happened already to set DP
# or we just have to have a dummy instruction.
0000 0000    mvi  r0,  DPlen=2   ; r0 discarded in this example
0000 0004    LongConst1          ; could be 64 bit or 128 or 256 bit
0000 0008    LongConst2          ; could be 64 bit or 128 or 256 bit
0000 000c    bne   x,  0, sety2
0000 0010    mvi   y, @DP#0   ; DP was set to 0000 0004 earlier
0000 0014    jmp   end
0000 0018    mvi   y, @DP#2   ; sety2
0000 001c    ....             ; end

the alternative, to save "wasting" an instruction (if there really
are no other prior immediates) is to actually set y unconditionally,
just to get the DataPointer set up then *conditionally* overwrite 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 285] bugzilla to be made available "offline"
From: bugzilla-daemon @ 2020-04-14 18:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-285-13@https.bugs.libre-soc.org/>

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

Jacob Lifshay <programmerjake@gmail.com> changed:

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

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
was going to half jokingly suggest the impractical (and probably insecure)
measure of putting the bugzilla installation in a public git repo --
bugs-everywhere looks much better, though I'd be concerned that we need a
working, secure, public https interface for those who don't want to install
bugs-everywhere locally and figure out how to use it. I know bugs-everywhere
has a interactive web interface, I just don't know if it properly supports
adding new users, authentication, etc.

-- 
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 285] bugzilla to be made available "offline"
From: bugzilla-daemon @ 2020-04-14 18:39 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-285-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Jacob Lifshay <programmerjake@gmail.com> ---
another option is fossil, which is a distributed version control system with a
wiki and bug tracker:
https://www.fossil-scm.org/home/doc/trunk/www/index.wiki

-- 
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 285] bugzilla to be made available "offline"
From: bugzilla-daemon @ 2020-04-14 18:55 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-285-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #1)
> was going to half jokingly suggest the impractical (and probably insecure)
> measure of putting the bugzilla installation in a public git repo --

sigh it'd involve dumping - then purging - parts of the bugzilla postgresql
dump.  bleh :)

> bugs-everywhere looks much better, though I'd be concerned that we need a
> working, secure, public https interface for those who don't want to install
> bugs-everywhere locally and figure out how to use it.

i'd want it anyway.

> I know bugs-everywhere has a interactive web interface, 

yes.  it's... "functional".

> I just don't know if it properly supports
> adding new users, authentication, etc.

wark-wark :)  not at all.  i believe it's there for "convenience", for
when you're running locally, and want to browse bugs, comment on them etc.
locally then "git push" out to merge with other users.

https://github.com/cherrypy/tools/blob/master/AuthenticationAndAccessRestrictions
or this
https://github.com/cherrypy/tools/blob/master/CASAuthentication

funfunfun...

sigh i kinda promised myself i wouldn't mess about with web frameworks any
more :)  however if my arm was sufficiently twisted i could likely throw
something together that's suitable for public use, maybe even (gosh)
using the bugzilla postgres user/pass to do it (!)

hm i wonder if we can justify putting in an NLNet Grant request specifically
for things like this, on the basis that, really, we do need full independence.
we could then find - and pay - someone to do these kinds of things.

-- 
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 285] bugzilla to be made available "offline"
From: bugzilla-daemon @ 2020-04-14 18:57 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-285-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #2)
> another option is fossil, which is a distributed version control system with
> a wiki and bug tracker:
> https://www.fossil-scm.org/home/doc/trunk/www/index.wiki

sigh i'd really like it... if they hadn't decided to reinvent git.
UNIX philosophy: do one thing, and do it well.  the majority of
other "project management" systems all allow alternative revision
control to be used.  an all-or-nothing approach does not inspire
confidence.

-- 
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-14 19:12 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzjHTsG3mcAWeKxb4cThrCD3ZBgfk8nry2=qLWoA9vHvw@mail.gmail.com>

https://www.youtube.com/watch?v=_5fmPpInJ7U

continuing the code-morph, i now have the FU-FU Matrices also working
with multiple GO-RD and GO-WR signals.  now to actually start using
them, which is where the fun starts. there are already several hundred
signals in the gtkwave files *sigh*...

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] LLHD: Rust is used to drive research in Hardware Design Languages
From: Jacob Lifshay @ 2020-04-14 23:01 UTC (permalink / raw)
  To: Libre-RISCV General Development

Found this very interesting paper on LLHD, a new IR for HDLs, in this
week's This Week in Rust:

https://arxiv.org/pdf/2004.03494

The website is:
http://llhd.io/

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

* Re: [libre-riscv-dev] LLHD: Rust is used to drive research in Hardware Design Languages
From: Luke Kenneth Casson Leighton @ 2020-04-14 23:21 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7puak40mJRbDn25BWk+m6kFvYzHsjJtnYuDX8GKDvC6w@mail.gmail.com>

On Wednesday, April 15, 2020, Jacob Lifshay <programmerjake@gmail.com>
wrote:

> Found this very interesting paper on LLHD, a new IR for HDLs, in this
> week's This Week in Rust:
>
> https://arxiv.org/pdf/2004.03494
>
> The website is:
> http://llhd.io/


aw not another one! and did they add it to yosys? if not it is
unfortunately just a toy.  yosys is the defacto standard gateway to FPGAs
and ASIC synthesis

l.



-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
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] LLHD: Rust is used to drive research in Hardware Design Languages
From: Jacob Lifshay @ 2020-04-14 23:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyjmV0mQES42dzvAdSi=hm83woZ9v3dEny5Cf97VkdZ+A@mail.gmail.com>

On Tue, Apr 14, 2020, 16:21 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Wednesday, April 15, 2020, Jacob Lifshay <programmerjake@gmail.com>
> wrote:
>
> > Found this very interesting paper on LLHD, a new IR for HDLs, in this
> > week's This Week in Rust:
> >
> > https://arxiv.org/pdf/2004.03494
> >
> > The website is:
> > http://llhd.io/
>
>
> aw not another one! and did they add it to yosys? if not it is
> unfortunately just a toy.  yosys is the defacto standard gateway to FPGAs
> and ASIC synthesis


Created an issue for adding RTLIL support:
https://github.com/fabianschuiki/llhd/issues/116

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

* Re: [libre-riscv-dev] LLHD: Rust is used to drive research in Hardware Design Languages
From: Luke Kenneth Casson Leighton @ 2020-04-14 23:49 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5JajsQS3nJAoBjhr3x-MZokUBOWaQd27SbtMK5-TP1sg@mail.gmail.com>

On Wednesday, April 15, 2020, Jacob Lifshay <programmerjake@gmail.com>
wrote:

>
>
> Created an issue for adding RTLIL support:
> https://github.com/fabianschuiki/llhd/issues/116


nice.


>
>

-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
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 286] DataPointer concept: long-immediate references
From: bugzilla-daemon @ 2020-04-15  6:41 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-286-13@https.bugs.libre-soc.org/>

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

cand@gmx.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cand@gmx.com

--- Comment #1 from cand@gmx.com ---
A banked data scheme, like on the 65816, would be a slightly simpler version.
Instead of incrementing a pointer, the data bank register contains the high
bits, and the instruction contains the low bits. Such a setup also lets you
access larger-than-11-bit immediates, and is basically MIPS's small data
section made customizable.

It would still be relocatable, just in 11 bit alignments. The linker would
adjust the set-data-bank-register instructions on program load, for
position-independent code.

-- 
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 286] DataPointer concept: long-immediate references
From: bugzilla-daemon @ 2020-04-15  9:10 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-286-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to cand from comment #1)
> A banked data scheme, like on the 65816, would be a slightly simpler
> version. Instead of incrementing a pointer, the data bank register contains
> the high bits, and the instruction contains the low bits.

that's the 2nd version i came up with

> Such a setup also
> lets you access larger-than-11-bit immediates,

however you still need bits (or an instruction) specifying the immediate width,
somehow.

which is why i borrowed a couple of bits from the immediate to do that.

> and is basically MIPS's small
> data section made customizable.

interesting. worth investigating.

> It would still be relocatable, just in 11 bit alignments. The linker would
> adjust the set-data-bank-register instructions on program load, for
> position-independent code.

nice.

my feeling is we should take thus seriously because large immediate data load
is such a massive part of programs yet they are highly space inefficient.

-- 
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 286] DataPointer concept: long-immediate references
From: bugzilla-daemon @ 2020-04-15  9:23 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-286-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from cand@gmx.com ---
Yes, the amount of instructions POWER needs to load a 64-bit immediate is not
very efficient.

-- 
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 286] DataPointer concept: long-immediate references
From: bugzilla-daemon @ 2020-04-15 10:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-286-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to cand from comment #3)
> Yes, the amount of instructions POWER needs to load a 64-bit immediate is
> not very efficient.

mitch alsup mentioned that those comprise something like 6% of all instructions
(!).  i'm blown away that this has been a missed opportunity to significantly
reduce code size and i-cache usage.  particularly as a reduction in i-cache
size obeys a square law reduction in power consumption.  therefore if we can
get it down 5% that's a 10.25% reduction in 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 174] NLNet 2019 Formal Standards OpenPOWER proposal 2019-10-046
From: bugzilla-daemon @ 2020-04-15 12:14 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-174-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |IN_PROGRESS

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
received signed MoU from Bob Goudriaan at NLNet (with thanks and gratitude)

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