Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* [libre-riscv-dev] [Bug 339] create POWER9 ROTATE pipeline
From: bugzilla-daemon @ 2020-05-22 17:41 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-339-13@https.bugs.libre-soc.org/>

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
examining the shift operations, they generate CR0, and optionally the
Arithmetic ones will set CA and also read carry in.

do the Arith Shift also set the overflow flag?

microwatt does not have OV set, which tends to suggest that we can drop XER.SO
from the output regspec for this pipeline.

-- 
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 313] Create Branch Pipeline for POWER9
From: bugzilla-daemon @ 2020-05-22 18:21 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-313-13@https.bugs.libre-soc.org/>

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

--- Comment #38 from Michael Nolan <mtnolan2640@gmail.com> ---
I have a formal proof for branches now, I handled the CRs in a similar way to
the CR unit so I know the CR handling is good.

-- 
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 335] Formal Correctness Proof for Branch pipeline
From: bugzilla-daemon @ 2020-05-22 18:24 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #1 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from
https://bugs.libre-soc.org/show_bug.cgi?id=313#38)
> I have a formal proof for branches now, I handled the CRs in a similar way
> to the CR unit so I know the CR handling is good.

great.  i notice the "not doing 32 bit" right now.

-- 
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 335] Formal Correctness Proof for Branch pipeline
From: bugzilla-daemon @ 2020-05-22 18:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
just did my usual makes-me-happy variable name munging

-- 
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 330] create POWER9 Logic Pipeline
From: bugzilla-daemon @ 2020-05-22 18:30 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-330-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #2)
> michael i am just reviewing the isatables for LOGICAL operations.  two
> things struck me:
> 
> 1. CR0 is apparently an input for OP_CNTZ but not an output, and we have no
> cr0 in LogicalInputData.

That's a mistake, fixing...

> 
> 2. i am not seeing any of the LOGICAL operations listed as needing carry in
> nor producing carry out.
> 
> looking here:
> https://libre-soc.org/openpower/isa/fixedlogical/
> 
> it does not appear that any or them set anything other than CR0 and that is
> an output only.

They shouldn't need carry no. 

BTW, did the logical pipe's output stage get replaced with common_output_stage?
The logical pipe test is broken and I'm not sure how to fix 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 335] Formal Correctness Proof for Branch pipeline
From: bugzilla-daemon @ 2020-05-22 18:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
mmm... what about when op.lk is zero?

when op.lk is zero, we don't want dut.o.lr.ok to be set.

there's four cases to be covered

* rec.lk true, LK true
* rec.lk false, LK true
* rec.lk true, LK false
* rec.lk false, LK false

i belive dut.o.lr.ok should only be set when rec.lk is true and LK is true

however if i put "Assert lr_ok.ok == 0" the proof fails, indicating
a potential problem?


--- a/src/soc/fu/branch/formal/proof_main_stage.py
+++ b/src/soc/fu/branch/formal/proof_main_stage.py
@@ -129,6 +129,8 @@ class Driver(Elaboratable):
                     with m.If(LK & rec.lk):
                         comb += Assert(lr_o.data == (cia + 4)[0:64])
                         comb += Assert(lr_o.ok == 1)
+                    with m.Else():
+                        comb += Assert(lr_o.ok == rec.lk)

                 # Check that CTR is decremented
                 with m.If(~BO[2]):

-- 
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 330] create POWER9 Logic Pipeline
From: bugzilla-daemon @ 2020-05-22 18:38 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-330-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #3)
> (In reply to Luke Kenneth Casson Leighton from comment #2)
> > michael i am just reviewing the isatables for LOGICAL operations.  two
> > things struck me:
> > 
> > 1. CR0 is apparently an input for OP_CNTZ but not an output, and we have no
> > cr0 in LogicalInputData.
> 
> That's a mistake, fixing...

ok excellent.  it didn't show up in the unit tests.

> > 
> > 2. i am not seeing any of the LOGICAL operations listed as needing carry in
> > nor producing carry out.
> > 
> > looking here:
> > https://libre-soc.org/openpower/isa/fixedlogical/
> > 
> > it does not appear that any or them set anything other than CR0 and that is
> > an output only.
> 
> They shouldn't need carry no. 

ok good to confirm.

> BTW, did the logical pipe's output stage get replaced with
> common_output_stage?

yes and common_input_stage as well.

> The logical pipe test is broken and I'm not sure how to
> fix it.

you might have been in between git pulls, can you try again?

-- 
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 335] Formal Correctness Proof for Branch pipeline
From: bugzilla-daemon @ 2020-05-22 18:42 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #4 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #3)
> mmm... what about when op.lk is zero?
> 
> when op.lk is zero, we don't want dut.o.lr.ok to be set.
> 
> there's four cases to be covered
> 
> * rec.lk true, LK true
> * rec.lk false, LK true
> * rec.lk true, LK false
> * rec.lk false, LK false
> 
> i belive dut.o.lr.ok should only be set when rec.lk is true and LK is true
> 
> however if i put "Assert lr_ok.ok == 0" the proof fails, indicating
> a potential problem?
> 
> 
> --- a/src/soc/fu/branch/formal/proof_main_stage.py
> +++ b/src/soc/fu/branch/formal/proof_main_stage.py
> @@ -129,6 +129,8 @@ class Driver(Elaboratable):
>                      with m.If(LK & rec.lk):
>                          comb += Assert(lr_o.data == (cia + 4)[0:64])
>                          comb += Assert(lr_o.ok == 1)
> +                    with m.Else():
> +                        comb += Assert(lr_o.ok == rec.lk)
>  
>                  # Check that CTR is decremented
>                  with m.If(~BO[2]):

Ah, it looks like power_decoder2 already handles this for us. It only sets
dec2.e.lk if the instruction has the lk flag set in the table, and LK is set in
the instruction field.

-- 
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 335] Formal Correctness Proof for Branch pipeline
From: bugzilla-daemon @ 2020-05-22 18:47 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #5 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #4)

> Ah, it looks like power_decoder2 already handles this for us. It only sets
> dec2.e.lk if the instruction has the lk flag set in the table, and LK is set
> in the instruction field.

yyeah i think that was me, doing something random (which i now don't
quite follow, but i did at the time).  this should be commented.

also it occurs to me that similar things need to be done to check that
{insert_data_thing}.ok == 0 at appropriate points, because the plan is to 
actually use those in the CompUnits, to set the "REQUEST_WRITE" flags.

if for example ctr.ok is set to 1 when it should not be, the CTR SPR
would get corrupted data sent to the register file.

-- 
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 316] bperm TODO
From: bugzilla-daemon @ 2020-05-22 18:49 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-316-13@https.bugs.libre-soc.org/>

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

--- Comment #93 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #92)
> Big endianess: LSB starts at top numbered wire, MSB is in wire 0.
> 
> little: LSB is in wire 0.
> 
> to access 64 bit in BE you do this
> x[63-index]
> not
> x[index]
> 
> to access 32 bit in BE you do this:
> x[31-index]
> 
> so somewhere, that is what is needed.

I think I've tried every possible combination at this point and I am still
unable to make progress. This is the current state of my bpermd.py module, that
at least doesn't just output 0 every time. I think I have tried all possible
permutations of 63-index and 7-index, but still cannot get it to produce
correct results. Can you please give me some guidance?

```
def elaborate(self, platform):
    m = Module()
    perm = Signal(self.width, reset_less=True)
    rb64 = [Signal(1, reset_less=True, name=f"rb64_{i}") for i in range(64)]
    for i in range(64):
        m.d.comb += rb64[i].eq(self.rb[63-i])
        rb64 = Array(rb64)
        for i in range(8):
            index = self.rs[8*(7-i)+8:8*(7-i):-1]
            idx = Signal(8, name=f"idx_{i}", reset_less=True)
            m.d.comb += idx.eq(index)
            with m.If(idx < 64):
                m.d.comb += perm[7-i].eq(rb64[63-idx])
    m.d.comb += self.ra[0:8].eq(perm)
    return m
```

-- 
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 335] Formal Correctness Proof for Branch pipeline
From: bugzilla-daemon @ 2020-05-22 18:50 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
                # Check that CTR is decremented
                with m.If(~BO[2]):
                    comb += Assert(dut.o.ctr.data == ctr_next)


i think... that one needs...

                comb += Assert(dut.o.ctr.data != BO[2])

does that look right?

-- 
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 335] Formal Correctness Proof for Branch pipeline
From: bugzilla-daemon @ 2020-05-22 18:50 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
>                 comb += Assert(dut.o.ctr.data != BO[2])

wait...             comb += Assert(dut.o.ctr.ok != BO[2])

-- 
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 335] Formal Correctness Proof for Branch pipeline
From: bugzilla-daemon @ 2020-05-22 19:00 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-335-13@https.bugs.libre-soc.org/>

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

--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
commit 6c74707101355960956055ee586e81c26914d2f0 (HEAD -> master, origin/master)
Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date:   Fri May 22 19:59:59 2020 +0100

    test branch ctr ok flag

-- 
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 339] create POWER9 ROTATE pipeline
From: bugzilla-daemon @ 2020-05-22 19:07 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-339-13@https.bugs.libre-soc.org/>

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

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
done, here, recorded the commit in case it needs to be reverted.

commit e8e10da8650ff797faaad320fbd8b442a4bc4f0e (HEAD -> master, origin/master)
Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date:   Fri May 22 20:06:41 2020 +0100

    remove sticky overflow from Shift Rot pipeline

-- 
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] daily kan-ban update 22may2020
From: Cole Poirier @ 2020-05-22 19:10 UTC (permalink / raw)
  To: Libre-RISCV General Development; +Cc: Libre-RISCV General Development
In-Reply-To: <CAPweEDwtA3H9yP0JGQ2CvoR0ZbT0O2hasTbqam+tw7zQmKJ=Dg@mail.gmail.com>

On May 22 2020, at 8:02 am, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> * attended both OpenPOWER weekly coffee calls which were nice to do,
> especially learning about microwatt first boot and also what Cesar does.
> both very cool.

Would you mind giving a one line description here of what Cesar does?
I'd be interested to know as well.

> y'know... i have to say, i am not often aware at the time because i take
> breaks and binge watch series episodes (Stargate SG1 at present, but only
> because i ran out of American Ninja Warrior episodes), but each day when
> actually written out does seem to be one hell of a lot.  this probably
> because i don't do anything else, the entire day.

From an outsiders perspective, Luke, it appears as if you never sleep!! :)

> * keep an eye out for Cole.  i couldn't work it out, either.  might need
> your help, Michael.

Appreciated, very much appreciated. I spent all of yesterday failing to
get bpermd to work correctly, upon reflection today, since I'm pretty
sure I've tried all possible reverse indexing (e.g. 63-i, 7-i)
permutations, I suspect that I may be missing a line? Or something else
that I causing my module to behave close-ish(very ish) to correctly,
since it produces bit patterns that are usually off-by-one but in
but the bit that is off tends to move around the 'result area' that is
the least significant byte of output ra.

> work some on the bperm module with Cole.
> --Michael

I appreciate it Michael, in the mean time, I will work on the corilis2
chroot script, I believe it is almost complete, just have to setup a
user-USERNAME.mk file that sets up the include paths for alliance correctly.

Cole

_______________________________________________
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] daily kan-ban update 22may2020
From: Tobias Platen @ 2020-05-22 19:18 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <3C8C9F70-B1BB-4A9C-8EEB-14EA91B6E0C4@getmailspring.com>

First I fixed a ModuleNotFoundError, afterwards I ran score6600_multi.py test case, where I tried to find out whats going wrong.
That took the whole day, and I still did not find the error.

Tobias

_______________________________________________
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] daily kan-ban update 22may2020
From: Luke Kenneth Casson Leighton @ 2020-05-22 19:33 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200522211859.e55b7b6db4ca41e768343ab7@platen-software.de>

On Fri, May 22, 2020 at 8:19 PM Tobias Platen
<libre-soc@platen-software.de> wrote:
>
> First I fixed a ModuleNotFoundError, afterwards I ran score6600_multi.py test case, where I tried to find out whats going wrong.
> That took the whole day, and I still did not find the error.

score6600_multi.py is not broken: the testing is

reg 0 expected 0 received 0 OK
reg 1 expected 1 received 1 OK
reg 2 expected 2 received 2 OK
reg 3 expected 3 received 3 OK
reg 4 expected 4 received 4 OK
reg 5 expected 5 received 5 OK
reg 6 expected 6 received 12 !ok   <- correct result
reg 7 expected 7 received 7 OK

the regfile / memory simulator in score6600_multi.py has not been
replaced with the one that michael wrote, hence why i have not updated
it.

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

* Re: [libre-riscv-dev] daily kan-ban update 22may2020
From: Jacob Lifshay @ 2020-05-22 19:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwtA3H9yP0JGQ2CvoR0ZbT0O2hasTbqam+tw7zQmKJ=Dg@mail.gmail.com>

working on mul and div units today, may not get much done due to less time
to work.

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] daily kan-ban update 22may2020
From: Luke Kenneth Casson Leighton @ 2020-05-22 20:04 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6BLzojD-WQB-POo_F39dvzpkQL9F_myMf_ex+_uosrEQ@mail.gmail.com>

On Fri, May 22, 2020 at 9:00 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> working on mul and div units today,

superb.

> may not get much done due to less time
> to work.

ok.

_______________________________________________
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] daily kan-ban update 22may2020
From: Luke Kenneth Casson Leighton @ 2020-05-22 20:12 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwBeyCPoJ-pAZ+0qLs5-6NWqTpKA6KJtY4BCNEQv=DtOw@mail.gmail.com>

the thought occurs to me jacob, if you can get the two pipelines
established (3rd add, carry in on the add side) michael and i can likely
link it together at the POWER9 side

On Friday, May 22, 2020, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> On Fri, May 22, 2020 at 9:00 PM Jacob Lifshay <programmerjake@gmail.com>
> wrote:
> >
> > working on mul and div units today,
>
> superb.
>
> > may not get much done due to less time
> > to work.
>
> ok.
>


-- 
---
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 340] New: formal proof of POWER9 SHIFTROT pipeline needed
From: bugzilla-daemon @ 2020-05-22 20:28 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 340
           Summary: formal proof of POWER9 SHIFTROT pipeline needed
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: Formal Verification
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

a formal proof of the POWER9 shiftrot function is needed

-- 
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 340] formal proof of POWER9 SHIFTROT pipeline needed
From: bugzilla-daemon @ 2020-05-22 20:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-340-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
    NLnet milestone|---                         |NLNet.2019.10.Formal
           Assignee|lkcl@lkcl.net               |mtnolan2640@gmail.com

-- 
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 340] formal proof of POWER9 SHIFTROT pipeline needed
From: bugzilla-daemon @ 2020-05-22 20:29 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-340-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
    parent task for|                            |195
  budget allocation|                            |

-- 
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 340] formal proof of POWER9 SHIFTROT pipeline needed
From: bugzilla-daemon @ 2020-05-22 20:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-340-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
 total budget (EUR)|0                           |250
  for completion of|                            |
       task and all|                            |
           subtasks|                            |

-- 
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 195] Formal correctness framework is needed for Power ISA
From: bugzilla-daemon @ 2020-05-22 20:31 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-195-13@https.bugs.libre-soc.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
   budget (EUR) for|10700                       |10450
 completion of task|                            |
   (excludes budget|                            |
       allocated to|                            |
          subtasks)|                            |

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