* Re: [libre-riscv-dev] Public Inbox
From: Veera @ 2020-04-02 12:52 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <3EFE94C3-B808-47AA-8106-E28982D007F8@gatech.edu>
On Tue, Mar 31, 2020 at 06:02:56PM +0000, Immanuel, Yehowshua U wrote:
> At some point, we should migrate all the mboxes from mailman into public inbox, to take advantage of public inbox’s search feature.
>
> Right now, public inbox only goes back until March 3 2020.
>
> Yehowshua
It archived only from when it started. To bring back previous ones we have
to import them from mailman2 mbox archive till date.
Regards,
Veera
_______________________________________________
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 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-02 15:06 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-269-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=269
--- Comment #6 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ok subdirectory-reader completed, it parses the markdown files and
creates a dictionary of instructions:
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/decoder/pseudo/pagereader.py;hb=HEAD
i therefore just completed a read on all pages at
http://libre-riscv.org/openpower/isa and made formatting-corrections
we *should* now be able to piece together code-generation followed by
actually plugging these into a simulator.
next task will be to auto-generate code-fragments.
--
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 275] New: errata in V3.0B spec pseudo-code, page 88
From: bugzilla-daemon @ 2020-04-02 16:07 UTC (permalink / raw)
To: libre-riscv-dev
http://bugs.libre-riscv.org/show_bug.cgi?id=275
Bug ID: 275
Summary: errata in V3.0B spec pseudo-code, page 88
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: ---
+++ b/openpower/isa/comparefixed.mdwn
@@ -103,13 +103,13 @@ X-Form
src1 <- GPR[RA].bit[56:63]
match <- (src1 = (RB)[00:07]) |
- match <- (src1 = (RB)[08:15]) |
- match <- (src1 = (RB)[16:23]) |
- match <- (src1 = (RB)[24:31]) |
- match <- (src1 = (RB)[32:39]) |
- match <- (src1 = (RB)[40:47]) |
- match <- (src1 = (RB)[48:55]) |
- match <- (src1 = (RB)[56:63])
+ (src1 = (RB)[08:15]) |
+ (src1 = (RB)[16:23]) |
+ (src1 = (RB)[24:31]) |
+ (src1 = (RB)[32:39]) |
+ (src1 = (RB)[40:47]) |
+ (src1 = (RB)[48:55]) |
+ (src1 = (RB)[56:63])
CR[4×BF+32] <- 0b0
CR[4×BF+33] <- match
CR[4×BF+34] <- 0b0
--
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 185] Getting 502 Bad Gateway when accessing bugzilla from archive.org
From: bugzilla-daemon @ 2020-04-02 17:50 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
Jacob Lifshay <programmerjake@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|--- |High
Severity|normal |critical
--- Comment #6 from Jacob Lifshay <programmerjake@gmail.com> ---
Now I'm getting 502 Bad Gateway from my local computer:
curl --verbose --ipv6 --no-progress-meter http://libre-riscv.org/ &> curl.log
produces:
* Trying 2a00:1098:82:f::1:80...
* Connected to libre-riscv.org (2a00:1098:82:f::1) port 80 (#0)
> GET / HTTP/1.1
> Host: libre-riscv.org
> User-Agent: curl/7.69.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 502 Bad Gateway
< Server: nginx
< Date: Thu, 02 Apr 2020 17:44:04 GMT
< Content-Type: text/html
< Content-Length: 166
< Connection: keep-alive
<
{ [166 bytes data]
* Connection #0 to host libre-riscv.org left intact
<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>
Either we should fix the server's config or remove the IPv6 DNS entry, since it
works through IPv4.
--
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] test_decoder_gas.py still fails after update for unknown reason
From: Tobias Platen @ 2020-04-02 18:04 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDzbnsgfK2JO=Xqin22jvcOEiM9hRM36KxZugCd-Bd7Qww@mail.gmail.com>
Now both test pass
Tobias
On Wed, 1 Apr 2020 15:16:22 +0000
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Wed, Apr 1, 2020 at 3:54 PM Michael Nolan <mtnolan2640@gmail.com> wrote:
>
> > This is fixed in soc/HEAD. My nmigen was a bit old so it didn't error on
> > my machine. Updating to latest nmigen let me reproduce the error.
>
> great. no need for a bugreport, then, tobias.
>
> yeh tracking latest nmigen is a bit of a pain.
>
> l.
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
--
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] submitted bugreport to upstream nmigen
From: Immanuel, Yehowshua U @ 2020-04-02 18:19 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyftS_SXb6Za4Oa6Ubs+Eg9C-3V0+ZvGVYtUhVukpmEiQ@mail.gmail.com>
> fantastic to hear that. must contact her and offer some € for nmigen
> work. in particular we need simulation of SR NAND latch and support
> for it to output into yosys.
Yes. Whitequark is great. I had contacted ‘quark some time ago about supporting her work directly.
It would be nice if we could support her work on YosysCXX too.
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
* [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway
From: bugzilla-daemon @ 2020-04-02 18:26 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
Luke Kenneth Casson Leighton <lkcl@lkcl.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|lkcl@lkcl.net |addw@phcomp.co.uk
--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
ngggh annoying. am going to assign this one to alain to investigate.
--
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] test_decoder_gas.py still fails after update for unknown reason
From: Luke Kenneth Casson Leighton @ 2020-04-02 18:33 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <20200402200404.2888ea1c6db1439cbd30f719@platen-software.de>
On Thu, Apr 2, 2020 at 7:04 PM Tobias Platen
<libre-soc@platen-software.de> wrote:
>
> Now both test pass
fantastic, good to hear.
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] virtual coffee again
From: Luke Kenneth Casson Leighton @ 2020-04-02 21:14 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyPSy58pSBGjGKTWsjU1k0V_qRBo69r9mhWbpcwwpBFHA@mail.gmail.com>
https://openpowerfoundation.org/openpower-virtual-coffee-calls/
2 hours from now (ok 1hr 45m)
On Thu, Apr 2, 2020 at 10:24 AM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:
>
> On Thu, Apr 2, 2020 at 9:57 AM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> >
> > https://openpowerfoundation.org/openpower-virtual-coffee-calls/
> >
> > remember UTC so calculate without timezones. 0900 UTC and 2200 UTC.
> > 0900 UTC is right now (3 mins)
>
> very short, next one 2200 UTC. better for USA. *remember it is UTC*
> so it is 2300 UK time for example.
>
> 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] finishing off the crowdsupply update
From: Jacob Lifshay @ 2020-04-02 22:59 UTC (permalink / raw)
To: Libre-RISCV General Development
what do we still need to do?
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] submitted bugreport to upstream nmigen
From: Jacob Lifshay @ 2020-04-03 4:10 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4ngnfC14SJOLAsemKPgA79qUzEqqKY+0MK+uavfz_Zsg@mail.gmail.com>
On Wed, Apr 1, 2020 at 8:03 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> Rerunning nmutil CI build to find the next errors:
> https://salsa.debian.org/Kazan-team/nmutil/-/jobs/642930
Fixed the remaining issues with nmutil, ended up adding
@unittest.skip() to 3 tests.
The CI build passes!
https://salsa.debian.org/Kazan-team/nmutil/-/jobs/644343
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
* [libre-riscv-dev] sorry state of ieee754fpu repo -- CI desperately needed
From: Jacob Lifshay @ 2020-04-03 7:04 UTC (permalink / raw)
To: Libre-RISCV General Development
The ieee754fpu repo is filled with tests that don't work because of
stuff like classes and imports being deleted/renamed, along with a few
files that are just syntatically incorrect. I've given up on cleaning
it up and having anything likely to still work by the time I'm done.
Luke, do you want to try to clean it up?
This is something that could have been caught before it descended into
chaos by having CI because it would fail and someone would get an
email when people break stuff, hence why I'm trying to add CI.
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
* [libre-riscv-dev] [Bug 276] New: SR NAND Latch needed in nmigrn
From: bugzilla-daemon @ 2020-04-03 10:00 UTC (permalink / raw)
To: libre-riscv-dev
http://bugs.libre-riscv.org/show_bug.cgi?id=276
Bug ID: 276
Summary: SR NAND Latch needed in nmigrn
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: lkcl@lkcl.net
CC: libre-riscv-dev@lists.libre-riscv.org
NLnet milestone: ---
The Dependency Matrices are huge and need SR NAND latches to get their size
down. This means we need to be able to express them in nmigen, perform some
form of equivalent simulation, and also have them passed through to yosys.
--
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Luke Kenneth Casson Leighton @ 2020-04-03 10:24 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD74QdtDc_7=ojaFc0ED4R3SzPGKS2b4s+mjshi-3ph=ag@mail.gmail.com>
On Fri, Apr 3, 2020 at 8:04 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> The ieee754fpu repo is filled with tests that don't work because of
> stuff like classes and imports being deleted/renamed, along with a few
> files that are just syntatically incorrect. I've given up on cleaning
> it up and having anything likely to still work by the time I'm done.
commit what you have. it doesn't surprise me because i stopped trying
to get the FSM functionality running, focussed instead on the
pipelines, and did a code reorg in the middle.
then nmigen has morphed as well and because the tests take so long i
haven't run them.
> Luke, do you want to try to clean it up?
deep breath: if it takes such a long time i am tempted to suggest that
we all tackle it (as and when).
> This is something that could have been caught before it descended into
> chaos by having CI because it would fail and someone would get an
> email when people break stuff, hence why I'm trying to add CI.
good call.
oh.
we need a CI output list.
_______________________________________________
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] finishing off the crowdsupply update
From: Luke Kenneth Casson Leighton @ 2020-04-03 10:28 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6pmTnpJO0yfmp-jPJjNF0LT7KFknqQ8ZGwGyCuFp2jUQ@mail.gmail.com>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Thu, Apr 2, 2020 at 11:59 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> what do we still need to do?
build server section and i think that's it. can you write sonething
short? about Cl
_______________________________________________
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Frieder Paape @ 2020-04-03 10:29 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDxvT1sqvKa6oq=_E25zM3wdmA5yeP3=3A8iMUkoW4PdzQ@mail.gmail.com>
Hi,
would setting up CI and fixing the tests be eligible for receiving NLnet
funding?
Frieder
On 2020-04-03 12:24, Luke Kenneth Casson Leighton wrote:
> On Fri, Apr 3, 2020 at 8:04 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>> The ieee754fpu repo is filled with tests that don't work because of
>> stuff like classes and imports being deleted/renamed, along with a few
>> files that are just syntatically incorrect. I've given up on cleaning
>> it up and having anything likely to still work by the time I'm done.
> commit what you have. it doesn't surprise me because i stopped trying
> to get the FSM functionality running, focussed instead on the
> pipelines, and did a code reorg in the middle.
>
> then nmigen has morphed as well and because the tests take so long i
> haven't run them.
>
>> Luke, do you want to try to clean it up?
> deep breath: if it takes such a long time i am tempted to suggest that
> we all tackle it (as and when).
>
>> This is something that could have been caught before it descended into
>> chaos by having CI because it would fail and someone would get an
>> email when people break stuff, hence why I'm trying to add CI.
> good call.
>
> oh.
>
> we need a CI output list.
>
> _______________________________________________
> 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] submitted bugreport to upstream nmigen
From: Luke Kenneth Casson Leighton @ 2020-04-03 10:37 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD4wCBySE0wT8O=zzH=8edyXw0bmd5LR1bMsYwfqm+TYaQ@mail.gmail.com>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Fri, Apr 3, 2020 at 5:10 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Wed, Apr 1, 2020 at 8:03 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > Rerunning nmutil CI build to find the next errors:
> > https://salsa.debian.org/Kazan-team/nmutil/-/jobs/642930
>
> Fixed the remaining issues with nmutil, ended up adding
> @unittest.skip() to 3 tests.
>
> The CI build passes!
exxcellent, that's really good news.
> https://salsa.debian.org/Kazan-team/nmutil/-/jobs/644343
*pauses*.... ah. i didn't realise that salsa - an external resource
not archived or under our direct control - had been selected for
creating information (reports) that is critically important to
preserve.
if we are kicked off of salsa or the service is terminated (debian
loses their sponsorship from gitlab) all those reports could be lost.
so we need to do three things:
1. work out how we managed to miss that, when it has been running for
such a long time already.
2. work out how we are going to archive the logs createe by Cl
3. wotk out if there is a way to get backups off of salsa of whatever
databases are being created .
_______________________________________________
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Luke Kenneth Casson Leighton @ 2020-04-03 10:48 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <2d0e9496-606a-4399-d35b-e90bfd87f896@paape.io>
On Fri, Apr 3, 2020 at 11:30 AM Frieder Paape <frieder@paape.io> wrote:
>
> Hi,
>
> would setting up CI
it should be (because retrospectively we should have thought aboit it)
however it was not planned, so no, unless we write a proposal to cover
it. this will involve specifically mentioning the fact that it is
documenting the ongoing success of the project, or something.
>and fixing the tests be eligible for receiving NLnet
> funding?
yes this one would be... except the only thing is we are almost out of
budget for the 2019-02-012 milestone covering the IEEE754 FPU.
and we cannot just take other budgets.
however what we can probably do is if other related tasks are
completed, perhaps those pay a tiny bit more generously (or, because
they were based on EUR living conditions, that may not be necessary)
regardless, we have to be extremely careful about that.
if we absolutely have to there does exist a cumulated budget from
Purism sponsorship. it is not huge.
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Frieder Paape @ 2020-04-03 10:52 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDyxxGGmYb3sA7ywrgSWT5njFT=EMVv3Ae=aguokMmD8PQ@mail.gmail.com>
Alright, it would finally be a chance for me to get a foot in the door
since gitlabs CI is something I know about and fixing tests will lead to
me getting an idea what the code is about.
On 2020-04-03 12:48, Luke Kenneth Casson Leighton wrote:
> On Fri, Apr 3, 2020 at 11:30 AM Frieder Paape <frieder@paape.io> wrote:
>> Hi,
>>
>> would setting up CI
> it should be (because retrospectively we should have thought aboit it)
> however it was not planned, so no, unless we write a proposal to cover
> it. this will involve specifically mentioning the fact that it is
> documenting the ongoing success of the project, or something.
>
>> and fixing the tests be eligible for receiving NLnet
>> funding?
> yes this one would be... except the only thing is we are almost out of
> budget for the 2019-02-012 milestone covering the IEEE754 FPU.
>
> and we cannot just take other budgets.
>
> however what we can probably do is if other related tasks are
> completed, perhaps those pay a tiny bit more generously (or, because
> they were based on EUR living conditions, that may not be necessary)
>
> regardless, we have to be extremely careful about that.
>
> if we absolutely have to there does exist a cumulated budget from
> Purism sponsorship. it is not huge.
>
> l.
>
> _______________________________________________
> 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
* [libre-riscv-dev] [Bug 276] SR NAND Latch needed in nmigen
From: bugzilla-daemon @ 2020-04-03 11:00 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-276-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=276
whitequark@whitequark.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |whitequark@whitequark.org
--- Comment #1 from whitequark@whitequark.org ---
(The following comment is copied from the email I sent earlier, so that it is
accessible publicly.)
Of the things you mentioned, this includes only the SR latch issue.
This issue is unfortunately quite involved. (n)Migen is designed to
connect large islands of purely synchronous logic with a few async
bridges. It does not, very deliberately, directly support arbitrary
asynchronous primitives like the SR latch. So you can't just drop one
into your design and have it work the same way normal logic works.
However, you're in luck because better support for asynchronous
signals was something I took into account when designing nMigen and
both of the new simulators, pysim and cxxsim.
To solve this issue, we'll need to work together to determine your
specific use case. Do you want to use the exact same netlist for
nMigen simulation and synthesis? If not, it means you can model
whatever it is that contains the SR latches (I'm not sure what
matrices you're referring to, here) using synchronous code, and
replace them with true SR latches for synthesis. Of course, you will
need to convince yourself these two designs are equivalent.
If you *do* want to use the exact same netlist, there are a few
options. Both the new nMigen simulator and cxxrtl use an architecture
that, in principle, supports logic feedback loops. So you can model
the SR latch using two ordinary NAND gates. If you have an instance
of a SRNAND cell, you can provide a simulation model for this instance
that uses two NAND gates, and it'll work. However, I must warn you
that both for nMigen pysim and cxxrtl, this will come with a severe
performance penalty of at least ~10x, possibly worse depending on your
exact design. If you are planning to use fine SRNAND cells (one per
bit rather than one per word), expect a further slowdown of the word
size factor. Another issue is that neither pysim nor cxxsim provide
any way to control the possible race conditions. That is, the SRNAND
latch that is simulated in pysim or cxxsim will initialize to
an indeterminate value, and chaining them together will lead to
unpredictable results.
--
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] sorry state of ieee754fpu repo -- CI desperately needed
From: Luke Kenneth Casson Leighton @ 2020-04-03 11:09 UTC (permalink / raw)
To: Libre-RISCV General Development
In-Reply-To: <76668cf6-f408-d206-9d01-afc7e7684c51@paape.io>
On Fri, Apr 3, 2020 at 11:52 AM Frieder Paape <frieder@paape.io> wrote:
>
> Alright, it would finally be a chance for me to get a foot in the door
> since gitlabs CI is something I know about and fixing tests will lead to
> me getting an idea what the code is about.
ok great.
jacob you good with that?
and with frieder helping on the backend server? (will need your ssh
pubkey, frieder)
we can, say, use... EUR 500 from the Purism budget, and see how it goes?
one top priority thing, working out how we can archive copies of all
messages generated by CI
and in particular, recover the ones already generated, even if it
means writing a web scraper.
we absolutely cannot rely on salsa as an uncontrolled resource. we
are guests on that machine and should in no way rely on that hosting
to continue to be provided (and no i am not running gitlab on the 1GB
memory allocation vCPU behind libreriscv!)
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] sorry state of ieee754fpu repo -- CI desperately needed
From: N.A. @ 2020-04-03 10:28 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDxvT1sqvKa6oq=_E25zM3wdmA5yeP3=3A8iMUkoW4PdzQ@mail.gmail.com>
Hi,
would setting up CI and fixing the tests be eligible for receiving NLnet
funding?
Frieder
On 2020-04-03 12:24, Luke Kenneth Casson Leighton wrote:
> On Fri, Apr 3, 2020 at 8:04 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>> The ieee754fpu repo is filled with tests that don't work because of
>> stuff like classes and imports being deleted/renamed, along with a few
>> files that are just syntatically incorrect. I've given up on cleaning
>> it up and having anything likely to still work by the time I'm done.
> commit what you have. it doesn't surprise me because i stopped trying
> to get the FSM functionality running, focussed instead on the
> pipelines, and did a code reorg in the middle.
>
> then nmigen has morphed as well and because the tests take so long i
> haven't run them.
>
>> Luke, do you want to try to clean it up?
> deep breath: if it takes such a long time i am tempted to suggest that
> we all tackle it (as and when).
>
>> This is something that could have been caught before it descended into
>> chaos by having CI because it would fail and someone would get an
>> email when people break stuff, hence why I'm trying to add CI.
> good call.
>
> oh.
>
> we need a CI output list.
>
> _______________________________________________
> 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] sorry state of ieee754fpu repo -- CI desperately needed
From: N.A. @ 2020-04-03 10:52 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <CAPweEDyxxGGmYb3sA7ywrgSWT5njFT=EMVv3Ae=aguokMmD8PQ@mail.gmail.com>
Alright, it would finally be a chance for me to get a foot in the door
since gitlabs CI is something I know about and fixing tests will lead to
me getting an idea what the code is about.
On 2020-04-03 12:48, Luke Kenneth Casson Leighton wrote:
> On Fri, Apr 3, 2020 at 11:30 AM Frieder Paape <frieder@paape.io> wrote:
>> Hi,
>>
>> would setting up CI
> it should be (because retrospectively we should have thought aboit it)
> however it was not planned, so no, unless we write a proposal to cover
> it. this will involve specifically mentioning the fact that it is
> documenting the ongoing success of the project, or something.
>
>> and fixing the tests be eligible for receiving NLnet
>> funding?
> yes this one would be... except the only thing is we are almost out of
> budget for the 2019-02-012 milestone covering the IEEE754 FPU.
>
> and we cannot just take other budgets.
>
> however what we can probably do is if other related tasks are
> completed, perhaps those pay a tiny bit more generously (or, because
> they were based on EUR living conditions, that may not be necessary)
>
> regardless, we have to be extremely careful about that.
>
> if we absolutely have to there does exist a cumulated budget from
> Purism sponsorship. it is not huge.
>
> l.
>
> _______________________________________________
> 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
* [libre-riscv-dev] [Bug 276] SR NAND Latch needed in nmigen
From: bugzilla-daemon @ 2020-04-03 12:05 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-276-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=276
--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to whitequark from comment #1)
> (The following comment is copied from the email I sent earlier, so that it
> is accessible publicly.)
appreciated, whitequark.
summary (the rest is archive-suitable / context) is: we'd like to be able
to do "exact" netlist (we already have semi-equivalent, and this is working).
> Of the things you mentioned, this includes only the SR latch issue.
>
> This issue is unfortunately quite involved. (n)Migen is designed to
> connect large islands of purely synchronous logic with a few async
> bridges. It does not, very deliberately, directly support arbitrary
> asynchronous primitives like the SR latch. So you can't just drop one
> into your design and have it work the same way normal logic works.
yes. very much aware that standard proprietary commercial tools completely
dropped support for SR latches.
(reiterating this for the archives:
however we really cannot use DFFs, here. that is 10 gates rather than 2,
and the number of Cells needed is massive: one of the Matrices may need
to be 128 x 30, with at least four maybe five latches per Cell. that's
192,000 gates *just for that Matrix* if we use DFFs.
if we use SR Latches, it's 38400 gates, which is tolerable)
> However, you're in luck because better support for asynchronous
> signals was something I took into account when designing nMigen and
> both of the new simulators, pysim and cxxsim.
whew :)
> To solve this issue, we'll need to work together to determine your
> specific use case. Do you want to use the exact same netlist for
> nMigen simulation and synthesis?
i honestly don't know: we're open to suggestions. (having read ahead)
if we can do both (and use one for rapid prototyping and the other as
a cross-check before moving to synthethis) that would be great.
right now we have something that "works" however
it uses DFFs, not SR latches (see latch.py link, below).
> If not, it means you can model
> whatever it is that contains the SR latches (I'm not sure what
> matrices you're referring to, here)
Out-of-Order Read/Write Hazard detection and avoidance matrices.
see "Modifications to Dependency Cell"
https://libre-riscv.org/3d_gpu/architecture/6600scoreboard/
* the DMs encode all registers in Unary (single bit activation).
thus one "row" represents all registers used for a given FunctionUnit
[and access to its ALU].
* each Cell thus records, in bit-level (unary) form, the fact that read/write
for a given function (add) is needed, by raising the "Reg 5 needs READ"
and "Reg 7 needs WRITE" SR Latches
* these now-active signals indicate to subsequent instructions
"hello i have a read hazard, hello i have a write hazard" respectively.
attempts to use those registers thus STOPs that FunctionUnit from executing.
* hazards get cleared out once results are written
* when there are zero hazards (in any given row), that instruction
becomes free-and-clear to proceed.
it's actually incredibly simple.
here's one for Register-to-FunctionUnit (FU being the "arbitrator" for access
to an ALU pipeline), you have to drill down a bit (through DependencyRow)
to get to the SR Latches themselves
https://git.libre-riscv.org/?p=soc.git;a=blob;f=src/soc/scoreboard/fu_reg_matrix.py;h=06380434c8d7d20828d80c3d0e020161bcb2c2e4;hb=b01f6bc0ad28cda131beae33e5fe338daaf5e9ea
> using synchronous code,
funnily enough that's where we are right now:
https://git.libre-riscv.org/?p=nmutil.git;a=blob;f=src/nmutil/latch.py;h=7d6a1efe22c881585a626e397590337186f6ef1b;hb=HEAD#l41
> and
> replace them with true SR latches for synthesis. Of course, you will
> need to convince yourself these two designs are equivalent.
yes. fortunately, coriolis2 has gate-level simulation (which needs
investigation) so we can triple-check.
> If you *do* want to use the exact same netlist, there are a few
> options. Both the new nMigen simulator and cxxrtl use an architecture
> that, in principle, supports logic feedback loops. So you can model
> the SR latch using two ordinary NAND gates. If you have an instance
> of a SRNAND cell, you can provide a simulation model for this instance
> that uses two NAND gates, and it'll work.
with the caveat that the current SRLatch class is actually a Reset-priority
SR latch, i *believe* we already have the former, so this latter is really
what we'd like to have.
we can always flip in/out the current SR Latch for a properly asynchronous
one (exact same netlist), run some (unbelievably slow) tests, then generate
the actual netlist to be handed to yosys (and from there to coriolis2).
> However, I must warn you
> that both for nMigen pysim and cxxrtl, this will come with a severe
> performance penalty of at least ~10x, possibly worse depending on your
> exact design. If you are planning to use fine SRNAND cells (one per
> bit rather than one per word), expect a further slowdown of the word
> size factor.
interesting, because a multi-word design turned out to be necessary
to get a speedup factor (some of the Matrices are so large - 128 x 30) that
we get seconds per clock in pysim if done as individual one-bit Cells.
the Matrices are so large - 128 x 30 will be the largest - that with a
4 to 5 level hierarchy of Elaboratable classes it was intolerable.
by removing one level of hierarchy, pysim ran in reasonable time.
i found this generally to be true: the more levels of hierarchy, the
slower pysim got. and due to the MASSIVE size of our designs, we need
hierarchically-laid-out classes (well over 250 so far).
> Another issue is that neither pysim nor cxxsim provide
> any way to control the possible race conditions. That is, the SRNAND
> latch that is simulated in pysim or cxxsim will initialize to
> an indeterminate value, and chaining them together will lead to
> unpredictable results.
you'll like this: it's much "worse" than it looks :) we actually have
a triple-connected ring of SRNAND latches, acting as a pseudo pipeline.
however, it turns out that the set-reset logic which *enables* the three
SRNANDs is very, very specifically organised such that only two of them
are ever possible to have active at any one time, and thus we create
a "revolving door" effect.
those "protections" are all synchronous. so whilst the SRNAND cells
are asynchronous and could hypothetically end up in "unknown", in
practice this can *never* occur because the conditions which create
"unknown" are specifically avoided (and avoided using synchronous
logic).
in case you were wondering: this is a proven design. it was used in the
original CDC 6600, and also in the AMD Opteron Series. however, in the
CDC 6600 they used transistors (as in: *actual* three-pronged transistors,
the largest ever single order made for transistors in the world), and
in the AMD Opteron Series they of course had the financial budget and
resources of a multi-billion-dollar company and so could happily pay for
custom silicon.
so. conclusion, after all that (apologies), is back at the top.
--
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 276] SR NAND Latch needed in nmigen
From: bugzilla-daemon @ 2020-04-03 12:11 UTC (permalink / raw)
To: libre-riscv-dev
In-Reply-To: <bug-276-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=276
--- Comment #3 from whitequark@whitequark.org ---
OK, having read that I suggest we follow the standard procedure. The new pysim
design should already handle this kind of logic loop just fine. I suggest you
make a (coarse) SRNAND latch out of normal (coarse) NAND cells, test that it
works correctly in your designs, and if it does not, file an MCVE over at the
nmigen repository. Then I investigate and fix any issues. The same with cxxsim
once it's ready.
Regarding hierarchical design slowdown: this is inevitable in the current pysim
architecture, but cxxsim can trivially use the Yosys flattening functionality
and does not suffer from any hierarchy-related issues.
--
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