* Re: [libre-riscv-dev] daily kan-ban update 13jul2020
From: Jacob Lifshay @ 2020-07-13 19:35 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200713203612.a464abb49dd8ed831e358a86@platen-software.de>
On Mon, Jul 13, 2020, 11:36 Tobias Platen <libre-soc@platen-software.de>
wrote:
> today:
>
> I've updated the .gitlab-ci.yml as it is missing a dependency
> (nmigen-soc).
> I was able to run the test_microwatt.py and test_issuer without any errors.
>
make sure to use https://github.com/nmigen/nmigen-soc.git since that
recently fixed a dependency issue that was causing nmigen to be reverted to
nmigen 0.1 from PyPI
>
> @programmerjake the .gitlab-ci.yml says
> https://github.com/nmigen/nmigen.git, is this correct.
>
yes, that is correct.
> First I tried out https://github.com/nmigen/nmigen.git which says
> nmigen-0.1 then
>
it's actually on nmigen-0.3-dev, you might have seen 0.1 from the
nmigen-soc dependency issue
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] xdc2020
From: Jacob Lifshay @ 2020-07-13 19:43 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4hQDPMwS=eFU2RX9C-ypy8jAO=PUnRq68zB=GGY1-mkA@mail.gmail.com>
On Fri, Jul 3, 2020, 11:50 Jacob Lifshay <programmerjake@gmail.com> wrote:
> do we want to submit a presentation at xdc2020 which is in september? it's
> now online and the submission deadline has been extended 2 weeks.
>
we're on the last week to make a submission
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] xdc2020
From: Jacob Lifshay @ 2020-07-13 19:46 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <5c2f4f78bb91d09160adc95f8296476c@f-cpu.org>
On Sat, Jul 4, 2020, 09:11 <whygee@f-cpu.org> wrote:
> On 2020-07-04 10:13, Jean-Paul Chaput wrote:
> > On Fri, 2020-07-03 at 14:56 -0700, Jacob Lifshay wrote:
> >> On Fri, Jul 3, 2020, 14:37 Luke Kenneth Casson Leighton
> >> <lkcl@lkcl.net> wrote:
> >>
> >> > libre :) it's not called open-soc
> >>
> >> FOSS for hardware, maybe FOSH?
> >
> > Just a small comment in passing, from our ASIC end point of view,
> > we try to promote the term "Free Silicon". This covers mostly the
> > tools, maybe not what you do with them, and for an X conference...
> >
> > Best regards,
>
> I can hear the voice of Richard Stallman ranting and fuming from here
> :-D
>
> "Free silicon" is not accurate : the silicon itself is not free, it's
> hardware.
>
we should strive towards the silicon being free as in freedom, so free
silicon is accurate, just easily confused with free as in $0. :)
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 13jul2020
From: Cole Poirier @ 2020-07-13 19:47 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5-QHbzEp774PGTZF7=hPsV4PS2Y5Qx6vfTBXKtZyLSfw@mail.gmail.com>
Yesterday:
* Updated dev-env-setup/hdl-dev-repos script to correctly set up nmigen-soc
* Started working on bringing
https://libre-soc.org/HDL_workflow/coriolis2/ up to date with
dev-env/setup/coriolis2-chroot
Today:
Continue working on updating the wiki documentation for setup of dev
environments. Luke I plan on also working on the alliance and
alliance-check-toolkit sections, as well as creating a section for
documenting our soclayout workflow. As far as I can tell this isn't
documented on the wiki, and I think it's important to have it well
documented as we are now ramping up the layout work with JP. I've
mostly been able to iron out the bugs in that workflow, but I may need
some help with configuration parameters, so I will comment on 'Bug 291
- HDL Workflow and Coriolis2 chroot automated setup scripts'
<https://bugs.libre-soc.org/show_bug.cgi?id=291> with my questions.
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] xdc2020
From: Cole Poirier @ 2020-07-13 19:49 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4ooG+n4p7U-qxCgSUU5b7tEZVaqNAcOXDv4OjqZTtj5A@mail.gmail.com>
On Mon, Jul 13, 2020 at 12:46 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> we should strive towards the silicon being free as in freedom, so free
> silicon is accurate, just easily confused with free as in $0. :)
We can call it Freedom Silicon? Like Freedom Fries ;-)
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] xdc2020
From: whygee @ 2020-07-13 21:19 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEg7hunhwmZLq3TaF+pBvZX=40WYtWRQBB3WvZdiQKX+h-ksFg@mail.gmail.com>
On 2020-07-13 21:49, Cole Poirier wrote:
> On Mon, Jul 13, 2020 at 12:46 PM Jacob Lifshay
> <programmerjake@gmail.com> wrote:
>
>> we should strive towards the silicon being free as in freedom, so free
>> silicon is accurate, just easily confused with free as in $0. :)
>
> We can call it Freedom Silicon? Like Freedom Fries ;-)
that sound familiar...
oh, yes :
https://www.drdobbs.com/open-hardware-aint-easy/184415121
it feels like y2k all over again ;-)
> Cole
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] daily kan-ban update 13jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-13 22:09 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEg7humyhx=ymYgyJoWjaE1KaVe3+JMmL7JEF5GFxxsOX_+mQg@mail.gmail.com>
On Monday, July 13, 2020, Cole Poirier <colepoirier@gmail.com> wrote:
> :
>
> Continue working on updating the wiki documentation for setup of dev
> environments. Luke I plan on also working on the alliance and
> alliance-check-toolkit sections,
excellent.
, so I will comment on 'Bug 291
> - HDL Workflow and Coriolis2 chroot automated setup scripts'
> <https://bugs.libre-soc.org/show_bug.cgi?id=291> with my questions.
good idea.
>
> Cole
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>
--
---
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] daily kan-ban update 14jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-14 12:20 UTC (permalink / raw)
To: Libre-RISCV General Development
task list:
https://bugs.libre-soc.org/showdependencytree.cgi?maxdepth=1&id=383&hide_
resolved=1
yesterday:
* got formal proof for extswsli working (w00t)
* closed more bugreports
* tried new cxxrtl Simulator
today:
* started on privileged instruction checking
rest of day:
* unit tests for priv instructions, need to set MSR PR bit in tests and see
if TRAP occurs
* look at SHIFTROT mask-based formal proofs.
l.
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
--
---
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] daily kan-ban update 14jul2020
From: Tobias Platen @ 2020-07-14 18:59 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDwitUAZWinrLC_jHPd8U_UiE4_5epsweWqr3dh8idCaKQ@mail.gmail.com>
On Tue, 14 Jul 2020 13:20:08 +0100
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
today:
more work on the dev-env-setup. I still get a
ModuleNotFoundError: No module named 'ieee754.part
and don't know which module to install
The nmigen version is 0.3.dev139+gd714d78
--
Tobias Platen <libre-soc[at]platen-software[dot]de>
_______________________________________________
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 14jul2020
From: Jacob Lifshay @ 2020-07-14 20:00 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200714205903.52aee30b242adc35a268e72b@platen-software.de>
On Tue, Jul 14, 2020, 11:59 Tobias Platen <libre-soc@platen-software.de>
wrote:
> On Tue, 14 Jul 2020 13:20:08 +0100
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> today:
> more work on the dev-env-setup. I still get a
> ModuleNotFoundError: No module named 'ieee754.part
> and don't know which module to install
> The nmigen version is 0.3.dev139+gd714d78
>
looks like someone forgot to add an empty __init__.py file to
ieee754fpu/src/ieee754/part/
go ahead and add it if you like
many of the tests have bitrotted since we never finished off getting CI
working
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 14jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-14 20:41 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200714205903.52aee30b242adc35a268e72b@platen-software.de>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, Jul 14, 2020 at 7:59 PM Tobias Platen
<libre-soc@platen-software.de> wrote:
>
> On Tue, 14 Jul 2020 13:20:08 +0100
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> today:
> more work on the dev-env-setup.
"python3 setup.py install" - this should be "python3 setup.py develop"
unless there is a specific reason why that should not be done?
https://bugs.libre-soc.org/show_bug.cgi?id=430
> I still get a
> ModuleNotFoundError: No module named 'ieee754.part
> and don't know which module to install
jacob replied, here.
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] Markdown on the wiki?
From: Luke Kenneth Casson Leighton @ 2020-07-15 10:05 UTC (permalink / raw)
To: Samuel Falvo II, Libre-RISCV General Development
In-Reply-To: <CAEz=somu-i6og_eQZ51WbbLSe8spGAzEHiXUiDAY6=gdx1vFOg@mail.gmail.com>
On Wed, Jul 15, 2020 at 2:40 AM Samuel Falvo II <sam.falvo@gmail.com> wrote:
>
> Hi Luke,
>
> I wrote up a summary of what I've learned by reviewing the source
> code. But, when I view the notes that I've written[1],
> https://libre-soc.org/Documentation/notes_on_formal_proofs/
excellent. i'll find a location for it. thank you for creating that page.
> the formatting
> of fixed-width code snippets enclosed in `backticks` results in the
> snippets being on a completely new HTML division, as if I'd written
> ```backticks``` instead.
yes. there's a bug where fixed-width code following bullet-points
does not get marked up as fixed-width. to sort that i had to change
the css:
https://libre-soc.org/local.css
> Is this a limitation of ikiWiki that cannot be easily fixed?
no - it's just a matter of someone having the time to properly investigate.
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] Markdown on the wiki?
From: Luke Kenneth Casson Leighton @ 2020-07-15 10:47 UTC (permalink / raw)
To: Samuel Falvo II, Libre-RISCV General Development
In-Reply-To: <CAPweEDySjucO9pRDOCYmnaeTtoE2RFpo6+++hTskGiLMWBtsow@mail.gmail.com>
On Wed, Jul 15, 2020 at 11:05 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Wed, Jul 15, 2020 at 2:40 AM Samuel Falvo II <sam.falvo@gmail.com> wrote:
> >
> > Hi Luke,
> >
> > I wrote up a summary of what I've learned by reviewing the source
> > code. But, when I view the notes that I've written[1],
> > https://libre-soc.org/Documentation/notes_on_formal_proofs/
>
> excellent. i'll find a location for it. thank you for creating that page.
i've put some comments inline, samuel, particularly referencing the
investigation last night and this morning:
https://bugs.libre-soc.org/show_bug.cgi?id=429#c3
if you create a bugreport for it we can actually put in an rfp for you
(request for payment) - it's a small budget for documentation.
key notes:
* the pipeline API is inviolate. you do not break it. *at no time*
will there *ever* be circumstances where it is bypassed. evverrrr.
* the only "exception" to that is LDSTCompUnit - and it achieves this
by *not using the pipeline API at all*.
* the ASCII art diagram is slightly misleading to refer to its inputs
and outputs as "Registers" because this could be confused with
"Register File".
* FPPipeContext (dut.o.ctx, dut.i.ctx) is not a Record. this would
have been the source of the issue you encountered
> > the formatting
> > of fixed-width code snippets enclosed in `backticks` results in the
> > snippets being on a completely new HTML division, as if I'd written
> > ```backticks``` instead.
>
> yes. there's a bug where fixed-width code following bullet-points
> does not get marked up as fixed-width. to sort that i had to change
> the css:
> https://libre-soc.org/local.css
i wrote some code last week which auto-altered all of the isa
pseudocode sections - every single one of which (hundreds) had that
bug i mentioned. having "fixed" that i've removed the css "code"
block change.
https://libre-soc.org/openpower/isa/
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] Markdown on the wiki?
From: Luke Kenneth Casson Leighton @ 2020-07-15 17:12 UTC (permalink / raw)
To: Samuel Falvo II, Libre-RISCV General Development
In-Reply-To: <CAPweEDymg2MFsUrM8fpEtzZ4=ES-RxA_ujLQwpO=tu=_+L7sYw@mail.gmail.com>
samuel, hi,
i updated the page you started, a bit more, this morning. you should be
getting the impression now as to why i described this pipeline as dead
simple to start from, because the code itself in spr main_stage.py really
does not actually do very much.
no regfile reading, no decisions, no instruction decoding: nothing. its
*sole* job is to process its inputs and create some outputs. it doesn't
even know which registers that data actually comes from or goes to because
*that is not its responsibility*.
thanks to the pipeline API it doesn't even need to know a thing about
pipelines or even how those are set up: you noted that stages are all
combinatorial.
all pipelines are designed this way, as pure combinatorial blocks.
therefore, the formal proofs for each stage are correspondingly trivial in
nature, too.
as you are discovering, the context *around* each pipeline is pretty
involved, especially when you compare it to e.g. Minerva, which is the main
other nmigen core around.
however Minerva is designed as a low performance 32 bit single issue
processor, where this is a high performance multi-issue parallel processor
with OoO instruction order preservation. data paths in Minerva are 32 bit,
addresses are 32 bit: we have a massive **256** bit wide data path and will
be doing at least a 48 bit physical address space.
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
* [libre-riscv-dev] travelling next 2 days.
From: Luke Kenneth Casson Leighton @ 2020-07-16 10:38 UTC (permalink / raw)
To: Libre-RISCV General Development
going to be busy. moving furniture. back friday night. *might* be able to
do openpower coffee tonight.
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
* [libre-riscv-dev] Fwd: openpower virtual coffee 10mins
From: Luke Kenneth Casson Leighton @ 2020-07-16 21:50 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw9CUrSHXhP7Sa4_oEbtrt7Bmy44u3xwDUcuGao1XvJoA@mail.gmail.com>
https://openpowerfoundation.org/openpower-virtual-coffee-calls/
--
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
--
---
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] daily kan-ban update 16jul2020
From: Jacob Lifshay @ 2020-07-17 4:32 UTC (permalink / raw)
To: Libre-RISCV General Development
today:
attended virtual coffee meeting -- lots of interesting conversation, like usual
added code to switch out div pipeline's udivrem core to different
implementations -- added an implementation that uses nmigen's div and
rem operators for testing rest of div pipeline -- will add a FSM-based
implementation soon
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 16jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-17 6:38 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5wD0CYN_6TxWUQVRuTrr7uwq3FKJtJ_gCgEpXFkDC58A@mail.gmail.com>
On Friday, July 17, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> today:
> attended virtual coffee meeting -- lots of interesting conversation, like
> usual
yeah :)
>
> added code to switch out div pipeline's udivrem core to different
> implementations --
i'm tempted to suggest making it possible to select the different
implementations, you know, by the soc.config structures you can see
building up, there.
then the code is still around and useable when we do the larger cores and
sqrt and rsqrt make it worthwhile to use pipelines.
but the abstraction layers building up because of that approach is getting
really high.
> added an implementation that uses nmigen's div and
> rem operators for testing rest of div pipeline -- will add a FSM-based
> implementation soon
star.
--
---
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] daily kan-ban update 16jul2020
From: Luke Kenneth Casson Leighton @ 2020-07-17 17:13 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5wD0CYN_6TxWUQVRuTrr7uwq3FKJtJ_gCgEpXFkDC58A@mail.gmail.com>
On Fri, Jul 17, 2020 at 5:32 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
> added code to switch out div pipeline's udivrem core to different
> implementations -- added an implementation that uses nmigen's div and
> rem operators for testing rest of div pipeline -- will add a FSM-based
> implementation soon
btw jacob i've been re-reading alu_hier.py - both of those classes -
ALU and DummyALU - *are* FSM-based (and obey the pipeline API).
i've taken a tag/snapshot of the pipeline work (div_pipeline) prior to
replacement, so we can always refer back to it. i'm strongly leaning
towards ripping out the entire lot. because of the abstraction of
using the ieee754fp code it's really hard to follow. even with 6 to 8
editor windows open i'm having a hard time keeping up with it.
so feel free to rip out the whole lot ok?
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] soc/libreriscv submodule (unintentionally?) reverted
From: Jacob Lifshay @ 2020-07-17 18:31 UTC (permalink / raw)
To: Libre-RISCV General Development
Luke, not sure if it was intentional, but in:
commit b4562c8aa2a29589f28a5ecf63611aa1a9515d54
Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Fri Jul 17 13:13:51 2020 +0100
whitespace
you reverted the libreriscv submodule from:
commit d83e5ccbacd56e762bedc660cdd930264e12b81b
Author: lkcl <lkcl@web>
Date: Wed Jul 15 21:32:32 2020 +0100
to:
commit 12e9237b896ad233cb18946b34dab17d976f415c
Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date: Mon Jul 13 19:03:42 2020 +0100
add mtmsrd pseudocode
Please check your submodules before committing
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] soc/libreriscv submodule (unintentionally?) reverted
From: Luke Kenneth Casson Leighton @ 2020-07-17 18:43 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5SFR5qjNBNBvhqeX1cDB2cJK5HtOJHJz4V6PZ5PU5mBg@mail.gmail.com>
On Friday, July 17, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
> Luke, not sure if it was intentional, but in:
> commit b4562c8aa2a29589f28a5ecf63611aa1a9515d54
> Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> Date: Fri Jul 17 13:13:51 2020 +0100
>
> whitespace
>
> you reverted the libreriscv submodule from:
> commit d83e5ccbacd56e762bedc660cdd930264e12b81b
arse. not again.
i review the git logs and if there is anything that says "updated
submodules" i pay attention. i missed it this time.
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
* [libre-riscv-dev] spr formal proof, NLNet RFPs
From: Luke Kenneth Casson Leighton @ 2020-07-17 18:51 UTC (permalink / raw)
To: Libre-RISCV General Development
samuel: next step is to move the task to "completed"
https://libre-soc.org/Samuel_A_Falvo_II/
given that you're in the U.S., unless you open yourself a Transferwise
online bank account (accepting EUR currency) NLNet have asked us to
submit non-EU Requests for Payment at reasonably large amounts so that
bank fees are not extortionate. (EU accounts including Transferwise
International online accounts they have zero bank fees)
basically, pick your next proof :) Trap, MUL, DIV, or ShiftRot
"rotate and clear",
they all need doing.
or if you get bored of that there is a key strategic piece of code that needs
writing: the LDSTSplitter.
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] spr formal proof, NLNet RFPs
From: Samuel Falvo II @ 2020-07-17 20:15 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDws_xR1OtcjP54qGo1RgKA7Gssy+=sYU_vGXN0mVXuS6g@mail.gmail.com>
Registered as a personal account for the time being.
I think, in the interests of just practicing on the code-base, I'll
stick with the ALU FV requirements for the time being. I'm just
becoming comfortable with spelunking that code. I'd like to feel
useful for a while before I start another task. :)
On Fri, Jul 17, 2020 at 11:52 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> samuel: next step is to move the task to "completed"
> https://libre-soc.org/Samuel_A_Falvo_II/
>
> given that you're in the U.S., unless you open yourself a Transferwise
> online bank account (accepting EUR currency) NLNet have asked us to
> submit non-EU Requests for Payment at reasonably large amounts so that
> bank fees are not extortionate. (EU accounts including Transferwise
> International online accounts they have zero bank fees)
>
> basically, pick your next proof :) Trap, MUL, DIV, or ShiftRot
> "rotate and clear",
> they all need doing.
>
> or if you get bored of that there is a key strategic piece of code that needs
> writing: the LDSTSplitter.
>
> l.
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
--
Samuel A. Falvo II
_______________________________________________
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] spr formal proof, NLNet RFPs
From: Luke Kenneth Casson Leighton @ 2020-07-17 20:40 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAEz=sokKL4aCbLYj7R4=_sedycOZvrcN0jHZUr9zH6EkUR2OBQ@mail.gmail.com>
On Friday, July 17, 2020, Samuel Falvo II <sam.falvo@gmail.com> wrote:
> Registered as a personal account for the time being.
>
> I think, in the interests of just practicing on the code-base, I'll
> stick with the ALU FV requirements for the time being. I'm just
> becoming comfortable with spelunking that code. I'd like to feel
> useful for a while before I start another task. :)
:)
well, the ALU pipeline correctness proof is done already, and the Logical
one.
Trap is like the "next least complicated" one, pretty much along the same
lines as SPR.
https://bugs.libre-soc.org/show_bug.cgi?id=421
MUL is more challenging (more involved) as there are sign-swapping, 32 bit,
64 bit, etc involved.
DIV *might* actually be straightforward to do hum except as a FSM it'll
need some timing logic.
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
* [libre-riscv-dev] Signal names for trap pipeline??
From: Samuel Falvo II @ 2020-07-18 0:58 UTC (permalink / raw)
To: Libre-RISCV General Development
I'm running into an irreconcilable property violations with the formal
properties for the trap main stage.
I'm noticing that there's repeated references to SRR0 and SRR1
registers in https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/trap/main_stage.py;h=325fb373546673df3ec19a15554e775bcc6fe9a9;hb=HEAD;
however, after spending about 30 minutes hacking away at what might be
the cause, I realized after reviewing the graphs in GTKWave that I
don't see these signals in either the top or the DUT module signals.
Looking in https://git.libre-soc.org/?p=soc.git;a=blob;f=src/soc/fu/trap/pipe_data.py;h=d2de8552a62a55bada4a5e83726c273ef943ac83;hb=HEAD
seems to confirm my suspicion that neither srr0 nor srr1 actually
exist; they are (confusingly) called fast1 and fast2. Double-checking
GTKWave's signal lists confirms that fast1 and fast2 exist.
Can anyone please advise on how to proceed? I see several ways of
resolving this going forward, but I need input from others:
1. Rename fast1 and fast2 to srr0 and srr1, or,
2. Keep fast1/fast2 and rebind them to srr0/srr1 in the main_stage.py
and prove_main_stage.py files, or,
3. ...?
Thanks.
--
Samuel A. Falvo II
_______________________________________________
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