* Re: [libre-riscv-dev] daily kan-ban update 28may2020
From: Alain D D Williams @ 2020-05-28 23:15 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyxRBy1DbnymncC5rP_vyDEFcquRFbqRjoCxor5bG_T0Q@mail.gmail.com>
On Fri, May 29, 2020 at 12:06:04AM +0100, Luke Kenneth Casson Leighton wrote:
> On Fri, May 29, 2020 at 12:02 AM Alain D D Williams <addw@phcomp.co.uk> wrote:
>
> > A virtual Debian 10 - oh, good looks as if it will work ... just need a few new
> > packages .... damn ! RFS out of space; so move & symlink.
>
> ah yes sorry, latex does historically come with a hell of a lot of
> packages. if you apt-get clean (or rm /var/lib/apt/cache/*.deb) you
> should get 300mb back, at least.
The VM was more to play with the latest debian than do real work ... I just
installed not really worrying about how it partitioned the disk. It gave RFS
5.5 GB. Thanks to whoever working on BSD invented the symbolic link!
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
_______________________________________________
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 28may2020
From: Luke Kenneth Casson Leighton @ 2020-05-28 23:13 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <36FA381D-E344-4158-80AE-70BD90962B7F@gatech.edu>
i like it. we should be able to do 24 GFLOPs btw. 800mhz (0.8ghz) x
4 (quad-core) x 4-wide FP32 - and FMACs are counted as 2 FP "ops".
l.
On Fri, May 29, 2020 at 12:09 AM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> Today:
>
> Finished a website with strikingly similar objectives to Libre-SOC.
> Could it be?
> Nah…
>
> https://systemeslibres.org <https://systemeslibres.org/>
>
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
_______________________________________________
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 28may2020
From: Yehowshua @ 2020-05-28 23:09 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <2AF535E9-B9D6-4794-B6D5-4DD62F3E2D06@getmailspring.com>
Today:
Finished a website with strikingly similar objectives to Libre-SOC.
Could it be?
Nah…
https://systemeslibres.org <https://systemeslibres.org/>
_______________________________________________
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 28may2020
From: Luke Kenneth Casson Leighton @ 2020-05-28 23:06 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200528230243.GG18639@phcomp.co.uk>
On Fri, May 29, 2020 at 12:02 AM Alain D D Williams <addw@phcomp.co.uk> wrote:
> A virtual Debian 10 - oh, good looks as if it will work ... just need a few new
> packages .... damn ! RFS out of space; so move & symlink.
ah yes sorry, latex does historically come with a hell of a lot of
packages. if you apt-get clean (or rm /var/lib/apt/cache/*.deb) you
should get 300mb back, at least.
> I'll get there.
:)
_______________________________________________
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 28may2020
From: Alain D D Williams @ 2020-05-28 23:02 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6engCH5VvAjs3gP1mR3ABWEOvMZwKD7QNMzjeROuyYtw@mail.gmail.com>
I'm fighting a war of attrition ... geting the latex environment to build for documentation.
It turns out that the version on my main machine is too old - running Centos 6,
I'm planning upgrade to centos 8 in the summer/autumn.
A virtual centos 8 - packages that are on centos 6 are not available here :-(
A virtual Debian 10 - oh, good looks as if it will work ... just need a few new
packages .... damn ! RFS out of space; so move & symlink.
I'll get there.
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
_______________________________________________
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] openpower virtual coffee call 28may2020, 90 minutes time
From: Luke Kenneth Casson Leighton @ 2020-05-28 21:59 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200528215105.GF18639@phcomp.co.uk>
On Thu, May 28, 2020 at 10:51 PM Alain D D Williams <addw@phcomp.co.uk> wrote:
> > gmail is a pain - it hides the subject line. i keep forgetting that.
>
> WHAT ! ?? Why ?
it scrolls off the top of the screen, only being shown at the very
top. also, visually, there's a box around the topic that attracts the
eye to the text, "hiding" the subjectline even at the first post.
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] openpower virtual coffee call 28may2020, 90 minutes time
From: Alain D D Williams @ 2020-05-28 21:51 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDzBenV=xsJJ+VmbGPeY66HbX2smaJY48E-Va0BOMj7BRA@mail.gmail.com>
On Thu, May 28, 2020 at 10:04:29PM +0100, Luke Kenneth Casson Leighton wrote:
> On Thu, May 28, 2020 at 9:37 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
> >
> > >
> > > subject line: "openpower virtual coffee call 28may2020, 90 minutes
> >
> > Ah reading… I should try it sometime.
>
> gmail is a pain - it hides the subject line. i keep forgetting that.
WHAT ! ?? Why ?
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
_______________________________________________
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] openpower virtual coffee call 28may2020, 90 minutes time
From: Luke Kenneth Casson Leighton @ 2020-05-28 21:04 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <E4474F78-DB99-41B5-A41F-824CCD800A10@gatech.edu>
On Thu, May 28, 2020 at 9:37 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> > subject line: "openpower virtual coffee call 28may2020, 90 minutes
>
> Ah reading… I should try it sometime.
gmail is a pain - it hides the subject line. i keep forgetting that.
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 28may2020
From: Jacob Lifshay @ 2020-05-28 20:51 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <2AF535E9-B9D6-4794-B6D5-4DD62F3E2D06@getmailspring.com>
yesterday:
added Rust models of div and mod instructions -- tested to match POWER9,
also switched output format to JSON to allow easier ingestion
plans for today:
attend OpenPower virtual coffee meeting
work more on mul and div pipelines
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] openpower virtual coffee call 28may2020, 90 minutes time
From: Yehowshua @ 2020-05-28 20:37 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDx91X1=E625qf0KEw2O6uuD+ihmTqfYZkmYmTn+G9fvjA@mail.gmail.com>
>
> subject line: "openpower virtual coffee call 28may2020, 90 minutes
Ah reading… I should try it sometime.
Yehowshua
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
* Re: [libre-riscv-dev] openpower virtual coffee call 28may2020, 90 minutes time
From: Luke Kenneth Casson Leighton @ 2020-05-28 20:35 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <75E1BD6E-DA12-4FC4-A164-E600C7B8014E@gatech.edu>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Thu, May 28, 2020 at 9:32 PM Yehowshua <yimmanuel3@gatech.edu> wrote:
>
> >
> > https://openpowerfoundation.org/openpower-virtual-coffee-calls/
> >
> > note the change of dial-in number (and change in zoom link).
> >
>
> Thanks for the link Luke. I’ll hop on. How long before it starts?
subject line: "openpower virtual coffee call 28may2020, 90 minutes
time" although it's now 85.
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] openpower virtual coffee call 28may2020, 90 minutes time
From: Alain D D Williams @ 2020-05-28 20:35 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <75E1BD6E-DA12-4FC4-A164-E600C7B8014E@gatech.edu>
On Thu, May 28, 2020 at 04:32:24PM -0400, Yehowshua wrote:
> >
> > https://openpowerfoundation.org/openpower-virtual-coffee-calls/
> >
> > note the change of dial-in number (and change in zoom link).
> >
>
> Thanks for the link Luke. I’ll hop on. How long before it starts?
11pm British Summer time ...90 minutes from the time of this email.
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
_______________________________________________
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-05-28 20:34 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 #51 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #50)
> "this is why i said to use treereduce. or, actually, now you can import
> ortreereduce, from soc.regfile.regfile."
saw commit d42161569bfaad5f0703f67d41634fd460719c1b
excellent. (btw remember to do whitespace and actual code-changes separately)
(In reply to Luke Kenneth Casson Leighton from comment #48)
> -----
>
> return m is missing.
return m is still missing. this will prevent the module from working,
because the AST - which was constructed by the elaborate function - is
entirely blank (None), due to the return result being implicitly None.
--
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] openpower virtual coffee call 28may2020, 90 minutes time
From: Yehowshua @ 2020-05-28 20:32 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxe5Pi5Jzz4ALiR0v6QcLLmEyKD_B_jd=yG2ZvhBMWr4g@mail.gmail.com>
>
> https://openpowerfoundation.org/openpower-virtual-coffee-calls/
>
> note the change of dial-in number (and change in zoom link).
>
Thanks for the link Luke. I’ll hop on. How long before it starts?
_______________________________________________
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] openpower virtual coffee call 28may2020, 90 minutes time
From: Luke Kenneth Casson Leighton @ 2020-05-28 20:28 UTC (permalink / raw)
To: Libre-RISCV General Development
https://openpowerfoundation.org/openpower-virtual-coffee-calls/
note the change of dial-in number (and change in zoom link).
_______________________________________________
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-28 20:27 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=353
--- Comment #20 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Cole Poirier from comment #18)
> (In reply to Luke Kenneth Casson Leighton from comment #13)
> > i suggest starting with two utterly different proofs, divided and isolated
> > with "if self.writethru". yes NOT m.If because python parameters != nmigen
> > AST.A
> >
> > then, to do a 4 way (dual nested) set of m.If on ren and wen.
> >
> > then, in EACH quadrant, do completely separate assertions.
> >
> > but before making those assertions, write out in words the expected
> > behaviour when the 4 way truth table of wen and ren occurs.
>
> I think I might not understand the functionality of the module enough to
> know the expected behaviour. Is it the case that if not writethru nothing is
> supposed to happen?
>
> Further with regard to Michael's comments about needing to use Initial() and
> ResetSignal() should I wrap the if writethru..else in a "with
> m.If(init)...with m.Else()" similar to proof_fu.py?
yyep.
> Is it the case that, if
> Initial() then do rd operations, and else do wr operations?
nnope. Initial() is just that: the initial conditions.
> Finally, with regard to the 4-way truth table, is this format close to
> correct?
>
> ```
> rd.ren wr.wen rd.data_o reg
> 0 0 x y
> 0 1 x y
> 1 0 x y
> 1 1 x y
> ```
yep. drop that into a comment in the code, so we can edit it before
implementing 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
* Re: [libre-riscv-dev] daily kan-ban update 28may2020
From: Luke Kenneth Casson Leighton @ 2020-05-28 20:03 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <2AF535E9-B9D6-4794-B6D5-4DD62F3E2D06@getmailspring.com>
On Thu, May 28, 2020 at 8:33 PM Cole Poirier <colepoirier@gmail.com> wrote:
> Continue working on proof_regfile.py with luke
(thank you to Michael for confirming about using "Initial()")
i'm currently doing a CompUnit version of ALU test_pipe_caller.py.
it's thrown a spanner in the works of MultiCompUnit interaction with
ready-valid signalling. DummyALU's ready-valid signalling is not good
enough: it doesn't conform to the nmutil pipeline API, and neither
does MultiCompUnit.
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-28 20:00 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=353
--- Comment #19 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Cole Poirier from comment #18)
> Further with regard to Michael's comments about needing to use Initial() and
> ResetSignal() should I wrap the if writethru..else in a "with
> m.If(init)...with m.Else()" similar to proof_fu.py? Is it the case that, if
> Initial() then do rd operations, and else do wr operations?
I don't know specifically for this module, but generally you want to make sure
that the module and control signals are initialized to a default state.
For instance, you're going to be proving that a write to a register works sort
of like this:
with m.If(Past(rd_en)):
comb += Assert(data_out == something)
However, on cycle 0, yosys may choose Past(rd_en) to be High, but no data will
be output because it didn't happen during the actual proof (basically, yosys
saves the past state of the signal to a register, which is then read whenever
you call Past(signal). But on cycle 0, that register has a random value)
If you wait one cycle (with m.If(~init)) before doing your assertion, you won't
have that issue because Past(signal) will return the actual value from the
cycle before.
However, if you decide to use the initial cycle to reset your register file,
you'll have other issues because you're resetting it at the same time you're
reading it, so once again your assertion will probably fail. To fix this, you'd
want to use an Assume to force rd_en (or whatever other signals you're using)
to be disabled during reset.
--
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-28 19:50 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=353
--- Comment #18 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #13)
> i suggest starting with two utterly different proofs, divided and isolated
> with "if self.writethru". yes NOT m.If because python parameters != nmigen
> AST.A
>
> then, to do a 4 way (dual nested) set of m.If on ren and wen.
>
> then, in EACH quadrant, do completely separate assertions.
>
> but before making those assertions, write out in words the expected
> behaviour when the 4 way truth table of wen and ren occurs.
I think I might not understand the functionality of the module enough to know
the expected behaviour. Is it the case that if not writethru nothing is
supposed to happen?
Further with regard to Michael's comments about needing to use Initial() and
ResetSignal() should I wrap the if writethru..else in a "with m.If(init)...with
m.Else()" similar to proof_fu.py? Is it the case that, if Initial() then do rd
operations, and else do wr operations?
Finally, with regard to the 4-way truth table, is this format close to correct?
```
rd.ren wr.wen rd.data_o reg
0 0 x y
0 1 x y
1 0 x y
1 1 x y
```
If not can you help me with a diagram or a link? I've looked for 4-way truth
tables via google and I just get basic boolean logic tutorials in the form of:
```
p q p AND q
0 0 0
0 1 0
1 0 0
1 1 1
```
--
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] daily kan-ban update 28may2020
From: Cole Poirier @ 2020-05-28 19:33 UTC (permalink / raw)
To: Libre-RISCV General Development
Yesterday:
Worked on proof_regfile.py, had to do a bit of a reorg at luke's
direction because I was mixing python and nmigen AST variables.
Today:
Continue working on proof_regfile.py with luke
_______________________________________________
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-28 16:41 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=353
Michael Nolan <mtnolan2640@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Source Code |Formal Verification
--
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 348] POWER9 SPR pipeline needed
From: bugzilla-daemon @ 2020-05-28 16:20 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-348-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=348
--- Comment #5 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #4)
> (In reply to Jacob Lifshay from comment #3)
> > (In reply to Luke Kenneth Casson Leighton from comment #1)
> > > if decode_spr_num(e_in.insn) = SPR_XER then
> > > -- bits 0:31 and 35:43 are treated as reserved and return 0s
> > > -- when read using mfxer
> >
> > from what I recall, at least some of the reserved XER bits are software
> > writable and need to be implemented.
>
> can you recall where and drop the relevant text and ref here? technically
> it is possible to shadow the bits from the slow SPR regfile but it is messy.
it's in section
3.2.2 Fixed-Point Exception Register page 50 (74 of PDF)
of Power ISA v3.1
<describing XER bit fields>
46:56 Reserved
Bits 48:55 are implemented, and can be read
and written by software as if the bits contained
a defined field.
57:63 This field specifies the number of bytes to be
transferred by a Load String Indexed or Store
String Indexed instruction.
Bits 48:55 of the XER correspond to bits 16:23 of
the XER in the POWER Architecture. In the
POWER Architecture bits 16:23 of the XER contain
the comparison byte for the lscbx instruction.
Power ISA lacks the lscbx instruction, but some
application programs that run on processors that
implement Power ISA may still use lscbx, and
privileged software may emulate the instruction.
XER48:55 may be assigned a meaning in a future
version of the architecture, when POWER compati-
bility for lscbx is no longer needed, so these bits
should not be used for purposes other than the
lscbx comparison byte.
--
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 331] Formal Correctness Proof for LOGICAL pipeline
From: bugzilla-daemon @ 2020-05-28 15:41 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-331-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=331
--- Comment #5 from Michael Nolan <mtnolan2640@gmail.com> ---
OP_SETB proof -
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=6b9d6a743b69bb9370ef1ed06cd89d10114edcf4
OP_ISEL proof -
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=27440addbb83c3c13949246b495b8c474b1c2c90
--
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 347] add setb (to CR pipeline?)
From: bugzilla-daemon @ 2020-05-28 15:39 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-347-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=347
Michael Nolan <mtnolan2640@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
CC| |mtnolan2640@gmail.com
Assignee|lkcl@lkcl.net |mtnolan2640@gmail.com
Resolution|--- |FIXED
--- Comment #1 from Michael Nolan <mtnolan2640@gmail.com> ---
Added OP_SETB to cr/main_stage.py:
https://git.libre-soc.org/?p=soc.git;a=commitdiff;h=9fc022b107d293611e70a54376bc10c78918a81b
--
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 353] formal proof of soc.regfile classes RegFile and RegFileArray needed
From: bugzilla-daemon @ 2020-05-28 14:18 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-353-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=353
Michael Nolan <mtnolan2640@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtnolan2640@gmail.com
--- Comment #17 from Michael Nolan <mtnolan2640@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #16)
> (In reply to Cole Poirier from comment #15)
>
> > Spent an hour trying to sense of this but I think my brain has given up for
> > the day. Will make a fresh effort tomorrow.
>
> did a bit of a reorg. i think we need to look at how proof_fu.py works.
> the use of "Initial()" may be crucial.
It is. From my experience doing formal stuff in verilog, if you use $past()
without making sure the module is properly reset, the proof engine will make up
values for the signals before the proof even starts. Making sure you have a
reset for the first cycle of the proof, and not examining any Past() signals on
that cycle will avoid this.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
^ permalink raw reply
page: next prev 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