Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] Following the PowerISA
From: Immanuel, Yehowshua U @ 2020-04-06  6:28 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <510B76DF-5A8A-4833-86E2-F5CA805A767C@gatech.edu>

https://libre-riscv.org/resources/

I’ve finished going through all the links on the resources page and performed a massive re-organization(basically moved links around into neat sections), and added a couple sections based on my research into the user demographic of POWER systems.

Request for comments…

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] Who Buys Talos Workstations?
From: Immanuel, Yehowshua U @ 2020-04-06  6:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzWMgbG8Q=YxYMChEdJXyMY5YAmD-cgFS5Khe3pdjDcWw@mail.gmail.com>

As mentioned earlier, I’ve been having some meetings at the startup school Create-X and one of the topics that comes up frequently concerns target markets, who else has had success in our space, and competitors.

One question I’ve been looking into is just how successful is FOSS/libre hardware, and who needs it?
I’ll add my findings to the wiki later.

Fantastic Interview with RaptorCS I found on the wiki resources page that talks about who needs open auditable systems that RaptorCS provides below:

https://www.youtube.com/watch?v=o5Ihqg72T3c&feature=youtu.be

Main benefits of POWER that I was able to glean:
 - POWER is really good at handling behemoth amounts of IO - far superior to x86
 - POWER works well with OpenCAPI, delivering somewhere near 5 - 10x speedup relative to PCIE Gen4
 - According to Raptor, IBM takes feedback on POWER ISA quite seriously and works hard to improve for next spec
 - Very easy to add data hungry accelerator to POWER systems, again, because of OpenCapi
 - RaptorCS customers tend to desire direct control over the on-mobo BMC, which RaptorCS provides through FOSS firmware - can guarantee physical hardware access not necessarily equal to root access
 - 99% of Debian APT supported - AMD ROCM works out of the box.

After some digging around, RaptorCS solutions are not necessarily too expensive, the hardware is enterprise grade and falls in that price bracket. Also, included in that higher price tag is the peace of mind knowing that your system is fully auditable.

I will add this information to the resources section soon.

# Commodity POWER hardware available:

You can buy a Raptor Blackbird 4-core POWER9 system for $1468. While this seems a bit expensive compared to a comparable high end i7 intel system, you get access to the processor data sheet, pinouts, and mobo. All firmware, etc. Also, OpenCAPI seems to be a big reason alone customers are wiling to pay the extra price tag.
https://www.raptorcs.com/content/BK1B01/intro.html


Lastly, any intel or AMD system integrator using an x86/64 chip is not even allowed to provide mobs schematics under NDA alone.

You can also by the T2080 chip from digikey for $273. It comes with a full data sheet and everything.
I couldn’t find any benchmarks, but from the spec sheet, I’d hazard performance is comparable to a mid end i5 processor. Makes sense that this chip see notable use in the auto and defense industry as it has respectable DSP capabilities. Its only viable ARM competitor is Nvidia Jetson which is notably cheaper. System integration with T2080 seems notably easier however as it is has no NDAs.
https://www.digikey.com/product-detail/en/nxp-usa-inc/T2080NXE8TTB/568-13639-ND/7648244


Conclusion:
RaptorCS clearly demonstrates that a FOSS hardware business model is economically feasible. Encouraging news for us!

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] GStreamer and RUST
From: Immanuel, Yehowshua U @ 2020-04-06  6:47 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CD24056E-979B-40AA-8E57-68E4755C2204@gatech.edu>

See here: https://gtk-rs.org/blog/2019/12/15/new-release.html

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] Following the PowerISA
From: Jacob Lifshay @ 2020-04-06  7:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <92ACECA3-94CB-4D09-8DCA-801C07F47EEC@gatech.edu>

On Sun, Apr 5, 2020, 23:29 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> https://libre-riscv.org/resources/
>
> I’ve finished going through all the links on the resources page and
> performed a massive re-organization(basically moved links around into neat
> sections), and added a couple sections based on my research into the user
> demographic of POWER systems.
>
> Request for comments…
>

Generally looks good to me!

I have published simple-soft-float, so have updated the IEEE754 section
with links. Also updated to state that both simple-soft-float and Berkeley
softfloat are libraries for emulating IEEE754 in software, only Berkeley
testfloat is software for testing FP implementations.

https://libre-riscv.org/resources/#ieee754testingemulation

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] GStreamer and RUST
From: Jacob Lifshay @ 2020-04-06  7:12 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CD24056E-979B-40AA-8E57-68E4755C2204@gatech.edu>

On Sun, Apr 5, 2020, 22:57 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> Eventually when we get around to the VPU, we’ll be working closely with
> Gstreamer, which, has new rust bindings available.
>

Yay! Hoping that a lot of their format parsers/decoders will be rewritten
in Rust, because those seem to have a disproportionate number of
memory-safety vulnerabilities due to being written in C and handling tons
of obscure and complex formats. Video files that can remotely take over
your computer are never a good idea.

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 283] reversion of fields.text to fields.txt needed
From: bugzilla-daemon @ 2020-04-06 10:19 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-283-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=283

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
*grumble* :)  ok.  that's probably the bit of the puzzle i couldn't
work out.  thanks jacob.

-- 
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] Open Power Registration
From: Luke Kenneth Casson Leighton @ 2020-04-06 10:21 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <6ADFDFD2-C9DB-4F63-9F9F-C1B147CDC3B9@gatech.edu>

On Mon, Apr 6, 2020 at 4:02 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:

> Are we officially a member of the OpenPower community yet?

it's... kinda not that formal, on account of the community being an open one.
OpenPOWER Foundation *membership* however is a different matter, and i
haven't asked.

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 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-06 10:29 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 #37 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #36)

> maintain a set of patches for fields.txt?

i really don't think that's a route that should be explored.
if the spec is "wrong" then we should be raising it with the
OpenPOWER Foundation as a bug.

deviating from the spec means that we have to explain to people
why that has been done.

it's unnecessary, as well.  the field names were designed to be
unique (*sigh* except they're not - SPR opcode field clashes with 
SPR the global dictionary of SPRs....)

-- 
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 283] reversion of fields.text to fields.txt needed
From: bugzilla-daemon @ 2020-04-06 10:33 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-283-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=283

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
oh, one annoying thing with git submodules i just discovered, jacob:
you have to "git pull" in the submodule then actually commit the
resultant modifications to .gitmodules

if you don't it can cause conflicts during merge/rebase.
just got badly caught out by that one, and couldn't recover 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] added CI to soc.git as well as attempting to fix all tests
From: Luke Kenneth Casson Leighton @ 2020-04-06 10:36 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7s5+NQ_TcKYg_cza7OSNQpLyP9eg82W9zdgreY0=9bnQ@mail.gmail.com>

On Mon, Apr 6, 2020 at 1:44 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Sun, Apr 5, 2020 at 5:17 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> >
> > I pushed a new branch with my changes since basically everything is
> > changed and I didn't split my commits up very well.
> > On my computer, out of 234 tests, there are 4 errors and 1 failure.

not bad.

> >
> > https://git.libre-riscv.org/?p=soc.git;a=commitdiff;h=refs/heads/fix-tests
>
> better url:
> https://git.libre-riscv.org/?p=soc.git;a=tree;h=refs/heads/fix-tests;hb=refs/heads/fix-tests

nice.

_______________________________________________
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-06 10:38 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6qcbiAiQSF=wszRRYgCpaSUorCbCZR6_mdj_Rgj2Feiw@mail.gmail.com>

On Mon, Apr 6, 2020 at 2:06 AM Jacob Lifshay <programmerjake@gmail.com> wrote:

> > Should be relatively easy to use gitlab's API.
>
> One idea is to store all the scraped build logs in a git repo, which
> makes it easy to move it around and incrementally download stuff.
> We're working on doing the same thing for the mailing list.

as long as it gets sent by email a list can be set up to archive from there.

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: Luke Kenneth Casson Leighton @ 2020-04-06 10:39 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6nw7pgNFug9yNiZ3uzGykPKe-Xq+4_+TOe_OKR6oOJvQ@mail.gmail.com>

On Mon, Apr 6, 2020 at 1:59 AM Jacob Lifshay <programmerjake@gmail.com> wrote:

> Luke, do note that we are currently relying on the combination of
> github and debian salsa to host Kazan's source code, so if they both
> kick us out, we'd have to move all the source. We could probably add
> some more mirrors using the above git-mirroring script since due to
> your selection of port 922 instead of port 22 for ssh, gitlab doesn't
> support push mirroring to libre-riscv.org.

blech.  maybe time to move to port 22.

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] Who Buys Talos Workstations?
From: Luke Kenneth Casson Leighton @ 2020-04-06 10:49 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <C9CF1146-A034-44EF-9379-366EE8414F28@gatech.edu>

On Mon, Apr 6, 2020 at 7:46 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> As mentioned earlier, I’ve been having some meetings at the startup school Create-X and one of the topics that comes up frequently concerns target markets, who else has had success in our space, and competitors.

whenever i have had conversations with people about EOMA68, that they
can instead of moving the *data* from device to device, move the
*computer* from device to device (Memory Card pause Computer Card)
they absolutely get it and are delighted and really enthusiastic and
supportive.

in the current world environment that becomes even more important.

the Intel Compute Card project only failed because Intel tried shoving
*hardware-level encryption* into the specification.  if you look up
NexDock's story, Chinese ODMs completely failed to be able to cope
with the "changes" required - the differences between this
insanely-complex requirement and what they normally "cookie-cut clone
and shove out the door", at the **BIOS** level.

USD 250,000 wasted later, NexDock, the *only* company to publicly tell
people that they were doing an Intel Compute Card product, gave up.

simplicity is key.  EOMA68 comprises 68 pins, being an Aggregation
Standard: a standard that aggregates *other* standards, those
standards (USB3, I2C, SD/MMC) being *decades* old *well-established*
and simple standards.

start small, think big.

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] Following the PowerISA
From: Luke Kenneth Casson Leighton @ 2020-04-06 10:51 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <68333793-489F-4F74-88C2-7DA0BCA206A6@gatech.edu>

On Mon, Apr 6, 2020 at 3:46 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> On the website, we have:
>
> > The Libre RISC-V Project is building a hybrid CPU/GPU SoC. As the name of the project implies,
> > we will be following the RISC-V ISA due to it being open-source and also because of the huge
> > software and hardware ecosystem building around it.
>
> Since we are now doing userspace RISCV+POWER and system-wide POWER, I imagine this section should be updated?

https://git.libre-riscv.org/?p=crowdsupply.git;a=commitdiff;h=69576cbd0ca58e98ebbf525d827b377fe7ad04fc

_______________________________________________
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] Following the PowerISA
From: Luke Kenneth Casson Leighton @ 2020-04-06 10:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <A03CD901-D668-44EC-8212-F63C65EA79E5@gatech.edu>

On Mon, Apr 6, 2020 at 3:54 AM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> Also on the website we have: https://libre-riscv.org/resources/#index9h1
>
>
> TODO get in touch: Other RISC-V GPU attempts
> • https://fossi-foundation.org/2019/09/03/gsoc-64b-pointers-in-rv32

the fossi foundation is run in... "Abusive Contributor Covenant
Conduct Mode" and they have unfortunately... abused that unethical
"Code".  therefore, sadly, the less we have to do with them, the
better.

> • http://bjump.org/manycore/
>
> • https://resharma.github.io/RISCV32-GPU/


> Did we ever contact them?

no.

> Should I do that?

i left the links there mostly to let people know that they exist, so
that there is a comparison.  i did however reach out to the opencores
non-shader-engine team.

this should probably be added as well
https://opencores.org/projects/wf3d
https://opencores.org/projects/opengfx430

oh.  must record this one somewhere
https://opencores.org/projects/video_systems

where the heck is it...

oo!
https://opencores.org/projects/gpu

hm, sorry, can't find it at the moment.  it was a non-shader design.

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] CI passes for soc.git!!!
From: Luke Kenneth Casson Leighton @ 2020-04-06 11:07 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD6UgDvO7LiH9BGju77=BFQfEHVuW=SdrAUvMD7w-V_tMw@mail.gmail.com>

On Mon, Apr 6, 2020 at 2:36 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Sun, Apr 5, 2020 at 5:44 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> >
> > On Sun, Apr 5, 2020 at 5:17 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > >
> > > I pushed a new branch with my changes since basically everything is
> > > changed and I didn't split my commits up very well.
> > > On my computer, out of 234 tests, there are 4 errors and 1 failure.
> > >
> > > https://git.libre-riscv.org/?p=soc.git;a=commitdiff;h=refs/heads/fix-tests
> >
> > better url:
> > https://git.libre-riscv.org/?p=soc.git;a=tree;h=refs/heads/fix-tests;hb=refs/heads/fix-tests

ah.  just noticed.  i really can't stand branches.  they quickly
become an absolute nuisance, losing work, stopping (necessary)
communication and isolating the people who work on them from
absolutely everyone else.

working on the same branch requires that people communicate effectively.

> CI passes!!!

hurrah :)

> https://salsa.debian.org/Kazan-team/soc/-/jobs/649686
>
> I added @unittest.skip() to test_iq, Luke or whoever can fix that test.

can you please merge what you did (and work in master in future unless
there's a really *really* compelling and critical reason for doing
so)?

thx jacob.

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 269] auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-04-06 11:18 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 #38 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
done, michael.  d0_d1_d2 is "non-standard".  probably should be dropped,
on reflection.


commit 3a40cddd16f77259c9f15edaa5aecb12f1a1324d (HEAD -> master, origin/master)
Author: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Date:   Mon Apr 6 12:15:28 2020 +0100

    add individual field-detection where field spec is "d0,d1,d2"



Form DX
    field d0 BitRange([(0, 16), (1, 17), (2, 18), (3, 19), (4, 20), (5, 21),
(6, 22), (7, 23), (8, 24), (9, 25)])
    field d1 BitRange([(0, 11), (1, 12), (2, 13), (3, 14), (4, 15)])
    field d2 BitRange([(0, 31)])
    field d0_d1_d2 BitRange([(0, 16), (1, 17), (2, 18), (3, 19), (4, 20), (5,
21), (6, 22), (7, 23), (8, 24), (9, 25), (10, 11), (11, 12), (12, 13), (13,
14), (14, 15), (15, 31)])
    field RT BitRange([(0, 6), (1, 7), (2, 8), (3, 9), (4, 10)])
    field XO BitRange([(0, 26), (1, 27), (2, 28), (3, 29), (4, 30)])

-- 
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] [OT] the microsoft hacker ("Baby Driver")
From: Luke Kenneth Casson Leighton @ 2020-04-06 11:26 UTC (permalink / raw)
  To: Libre-RISCV General Development

http://lkcl.net/poems/poem20.html

my mama was an alien,
my daddy was an engineer,
and i was spawned from the borg one morn
with keeeeyboards in my ears, in my eeeeearrs.
...

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

:)

_______________________________________________
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 280] POWER spec parser needs to support fall-through cases
From: bugzilla-daemon @ 2020-04-06 12:33 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-280-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=280

--- Comment #7 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
blegh.  does the job.

+    """add annoying "silent keyword" (fallthrough)
+
+    this which tricks the parser into taking the (silent) case statement
+    as a "small expression".  it can then be spotted and used to indicate
+    "fall through" to the next case (in the parser)
+
+    bugs: any function that starts with the letters "case" or "default"
+    will be detected erroneously.  fixing that involves doing a token
+    lexer which spots the fact that "case" and "default" are words,
+    separating them from space, colon, bracket etc.
+    """
+    res = []
+    prev_spc_count = None
+    for l in code.split("\n"):
+        spc_count = count_spaces(l)
+        nwhite = l[spc_count:]
+        if nwhite.startswith("case") or nwhite.startswith("default"):
+            #print ("case/default", nwhite, spc_count, prev_spc_count)
+            if (prev_spc_count is not None and
+                prev_spc_count == spc_count and
+                (res[-1].endswith(":") or res[-1].endswith(": fallthrough"))):
+                res[-1] += " fallthrough" # add to previous line
+            prev_spc_count = spc_count
+        else:
+            #print ("notstarts", spc_count, nwhite)
+            prev_spc_count = None
+        res.append(l)
+    return '\n'.join(res)
+

-- 
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 280] POWER spec parser needs to support fall-through cases
From: bugzilla-daemon @ 2020-04-06 12:45 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-280-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=280

--- Comment #8 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
@@ -152,6 +154,8 @@ def annoying_case_hack_filter(code):
     for l in code.split("\n"):
         spc_count = count_spaces(l)
         nwhite = l[spc_count:]
+        if len(nwhite) == 0: # skip blank lines
+            continue
         if nwhite.startswith("case") or nwhite.startswith("default"):
             #print ("case/default", nwhite, spc_count, prev_spc_count)
             if (prev_spc_count is not None and
@@ -473,9 +477,11 @@ switch (n)

that was enough to get it to skip blank lines.  it "Does The Job".

yes it's not "clean / nice" however it's quick and it works.
moving on to the next task, kinda important.

-- 
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 217] create a "ring" system which allows pad locations to be specified conveniently
From: bugzilla-daemon @ 2020-04-06 14:18 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-217-13@http.bugs.libre-riscv.org/>

http://bugs.libre-riscv.org/show_bug.cgi?id=217

--- Comment #50 from Jock Tanner <tanner.of.kha@gmail.com> ---
Sorry for another big delay on my part.

(In reply to Luke Kenneth Casson Leighton from comment #45)
> so could you track down that auto-box-size computing function and then
> look at removing all hard-coded parameters?

'Module.compute_ab()' added.

> you'll likely need to run add.build() manually, then sub.build() manually,

I kinda anticipated such changes in workflow, so I divided the submodules
processing into 'build()' and 'place()' phases beforehand. Now I added an
utilities such as 'Module.submodules' iterator and
'Module.find_submodule(name)'.

> *then* in ALU16()'s build constructor it will have access to the
> (computed) width+height of each,

Also not a problem: after 'build_submodules()' it can be accessed via
submodule's 'ab' property.

> *then* it can compute its width and
> height.

Here I stumbled on how to get the end result.

> ALU16 computes its height based on:
> max(Add.H, Sub.H, middle-stuff-H) + 100 (to give room for the routing)
> 
> and its width based on:
> Add.W + Sub.W + middle-stuff-W + 20-or-so

I tried this approach, but middle stuff size calculates as 650×650 and
everything bloats. And there are many “unplaced design” errors. =(

-- 
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] CI passes for soc.git!!!
From: Jacob Lifshay @ 2020-04-06 14:37 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyoA3Om+dtOpsEnCnSdHFPHBS6E3SA_gVTwHfTFH8D=1w@mail.gmail.com>

On Mon, Apr 6, 2020, 04:08 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

>
> can you please merge what you did (and work in master in future unless
> there's a really *really* compelling and critical reason for doing
> so)?
>

So, just merge despite the commit mess?

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] Removing orphan pages from the wiki
From: Immanuel, Yehowshua U @ 2020-04-06 14:55 UTC (permalink / raw)
  To: Libre-RISCV General Development

The wiki has some orphan pages in the git Repo…

I’ll reply back with the list of files later, but, we should probably clean this up.

Also, @Luke, do you think you could add “Updates” to the toolbar, linking to the Crowd Supply page?

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] Removing orphan pages from the wiki
From: Immanuel, Yehowshua U @ 2020-04-06 14:57 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <81FEF361-F930-4827-8204-5B89A14DDEA2@gatech.edu>

> Also, @Luke, do you think you could add “Updates” to the toolbar, linking to the Crowd Supply page?

Navbar - not toolbar - LOL.

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] nlnet 2019 standards update - video and 3d acceleration standards
From: Immanuel, Yehowshua U @ 2020-04-06 16:02 UTC (permalink / raw)
  To: Libre-RISCV General Development

https://libre-riscv.org/nlnet_2019_standards/

 - Is this NLNet grant still valid now that we have moved to POWER?
 - Do we need to update the objectives a little since we are now on POWER?

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

page:   latest

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git