Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] Clock Gating (was cache SRAM organisation)
From: Luke Kenneth Casson Leighton @ 2020-03-28 14:26 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <0d35e45bd81eeaecedeb64dc5061c1e33c89630c.camel@fibraservi.eu>

On Sat, Mar 28, 2020 at 2:08 PM Staf Verhaegen <staf@fibraservi.eu> wrote:

> There is an (IMO better) alternative for what you are doing with your pass-through registers and that is clock gating (wikipedia, allaboutcircuits).

ok that's very valuable and appreciated.  will reply here
http://bugs.libre-riscv.org/show_bug.cgi?id=270

_______________________________________________
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 270] New: investigate nmigen clock gating
From: bugzilla-daemon @ 2020-03-28 14:14 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 270
           Summary: investigate nmigen clock gating
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                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: ---

see
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-March/005482.html

-- 
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] Clock Gating (was  cache SRAM organisation)
From: Staf Verhaegen @ 2020-03-28 14:08 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDzAtWoU+wc6MTayF1vtKJvrxLLfP-Q1Czea+NX5MgOrfg@mail.gmail.com>

[-- Attachment #1.1: Type: text/plain, Size: 3398 bytes --]

Luke Kenneth Casson Leighton schreef op vr 27-03-2020 om 10:59 [+0000]:
> On Fri, Mar 27, 2020 at 10:36 AM Staf Verhaegen <staf@fibraservi.eu> wrote:
> > Yes and no, it is the basic functionality of a pipeline :(
> 
> yes.
> > You have the same latency but can have double the number of operations in flight.
> 
> yes.  hence why it is so important to have, because double the numberof operations means that we need double the number of Function Unitsin the Dependency Matrix in order to keep the entire out-of-orderengine occupied.
> also, double the number of operations in flight means that we needdouble the number of Branch Prediction Units, and much more complexBPUs at that, just to deal with the (now very likely) scenario ofhaving far more overlapping inner loops "in flight".
> all this from just extending the pipeline length(s) from 5 to 10.  soit's not just a "nice-to-have" feature, it's actually really importantto keeping the overall size of the chip down.

There is an (IMO better) alternative for what you are doing with your pass-through registers and that is clock gating (wikipedia, allaboutcircuits).
The principle is that you save power by not clocking the parts of the circuit that don't have to do any computing. I think this could be a more general way to only enable the stages in your pipeline who actually are doing computation.
In the above example you would always use a 10 stage pipeline running at 1600MHz but to mimic the 5-stage pipeline you only submit an operation every other clock cycle and intermittently enable the odd and even stages in your pipeline. This way the MUXes are removed from the computation path.
Using a shift register it could be easily generalized to only enable the stages for which there is an operation going through the pipeline. When an operation is submitted you set the first bit in the shift register to enable the first stage in the pipeline. With each cycle you then shift this bit so the stage that is needed for the execution of that operation is active.
This is generalized power optimization because it means that if you are running a program that only uses integer operations your FPU and GPU with use almost no power.

The way to implement it is using EnableInserter. Some untested code how I think it can be done:

	stages_en = Signal(10)
	stage1 = EnableInserter(stages_en[0])(Stage1())
	stage2 = EnableInserter(stages_en[1])(Stage2())
	...

	m.d.sync += stages_en.eq(Cat(newop, stages_en[0:9]))

That said I think this feature does not fit in the MVP scope of the October prototype so that chip should IMO not use clock gating nor the pass-through register feature from the original discussion. Reason is that implementing it is easier said than done. Several things need to be done:
- You first need a clock gating cell. This is not available in nsxlib and is currently not planned to be implemented. I don't want to commit to something extra for the May test chip tape-out either.
- nmigen/yosys needs to properly support clock gating for ASICs. Likely this means work in yosys that insert the clock gates from if clauses in the RTL.
- Your P&R tool (e.g. Coriolis) needs to support the clock gates. It means your clock tree synthesis (CTS) needs to support more than just buffers in the clock tree. This is not a simple task and has to be discussed with Jean-Paul & co.

greets,
Staf.

[-- Attachment #2: Type: text/plain, Size: 177 bytes --]

_______________________________________________
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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-28 11:52 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzdUCst63B3ZFh6jyqLexdq3SjmUstJ=n9dNY=pMT_HyA@mail.gmail.com>

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

On Fri, Mar 27, 2020 at 7:20 PM Luke Kenneth Casson Leighton
<lkcl@lkcl.net> wrote:

> my feeling is, we're wasting our time trying to "manually" create both
> a processor and also a simulator, from "scratch", when there are
> perfectly good, machine-readable expressions (at least for the integer
> instructions), like this:

captured here:
http://bugs.libre-riscv.org/show_bug.cgi?id=269

let's discuss that on that bugreport.

btw, one important thing: the "original" NLNet Grant is *running low*
because of our need to transfer to POWER ISA (the expectation was to
use an existing RV codebase such as minerva and jump-start straight
from running working code).

therefore, the way we need to do this is for people to pitch in with
other tasks that *are* allocated new budgets, such as the Simulator,
formal proofs, and so on.

this means we need to *up our game* somewhat because we'll need to
work collaboratively and keep in touch regularly.  suggestions on how
to do that appreciated.

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] New: auto-conversion / parser of POWER ISA Spec v3.0B
From: bugzilla-daemon @ 2020-03-28 11:12 UTC (permalink / raw)
  To: libre-riscv-dev

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

            Bug ID: 269
           Summary: auto-conversion / parser of POWER ISA Spec v3.0B
           Product: Libre-SOC's first SoC
           Version: unspecified
          Hardware: PC
                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: ---

see
http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2020-March/005470.html
and
http://lists.mailinglist.openpowerfoundation.org/pipermail/openpower-hdl-cores/2020-March/000007.html

the idea is, rather than write the simulator (and hardware) by hand
(which will be tedious, slow, and full of mistakes), parse the pseudo-code
*in the spec*, and turn it into *actual code*.

-- 
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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-28 10:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <8fb9dbcc812d3d7050c6e336dc9bf68f88536888.camel@gmail.com>

On Saturday, March 28, 2020, Jock Tanner <tanner.of.kha@gmail.com> wrote:

> Hi!
>
> On Thu, 2020-03-26 at 21:03 +0000, Luke Kenneth Casson Leighton wrote:
> > * jock on how you got on with the coriolis2 thing (even if it's "it
> > was total chaos")
>
> > if you prefer just reply to this message with a paragraph or two and
> > i
>
> I also can not put my first impressions in just one or two paragraphs,
> so I wrote two versions. Luke, please choose the most appropriate one.


short for thecrowdsupply update, with a link here for the people interested
to read.  also i will specially include the insights about putting people
off due to the nonstandard style., that's quite important.

nicely done jock.



>
> Short version (TL/DR)
> =====================
>
> As a humble Python developer, I understand the unique status and
> significance of the Coriolis project, nevertheless I cannot help but
> notice that it has a huge room for improvement. I genuinely hope that
> my participation in libre-riscv will also help improve Coriolis.
>
>

-- 
---
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] extremely busy crowdsupply update started
From: Jock Tanner @ 2020-03-28  8:09 UTC (permalink / raw)
  To: Luke Kenneth Casson Leighton, Libre-RISCV General Development,
	Immanuel, Yehowshua U, Michael Nolan
In-Reply-To: <CAPweEDw_h8VQ3JJFF3FXph7Eg0ucVknuvMk=Xc0jSp0WP13=UQ@mail.gmail.com>

Hi!

On Thu, 2020-03-26 at 21:03 +0000, Luke Kenneth Casson Leighton wrote:
> * jock on how you got on with the coriolis2 thing (even if it's "it
> was total chaos")

> if you prefer just reply to this message with a paragraph or two and
> i

I also can not put my first impressions in just one or two paragraphs,
so I wrote two versions. Luke, please choose the most appropriate one.

Short version (TL/DR)
=====================

As a humble Python developer, I understand the unique status and
significance of the Coriolis project, nevertheless I cannot help but
notice that it has a huge room for improvement. I genuinely hope that
my participation in libre-riscv will also help improve Coriolis.

Detailed version (The Rant)
===========================

1. Installation

Coriolis 2 can be built and installed two ways:

  a) inside the home directory (“Fixed directory tree”), using a helper
script [1],
  b) as a package, either RPM or DEB [2].

I followed the (a) route, and it actually went well except for a couple
of quirks, that is considering the number of dependencies. As I
understand, the (b) way is not well maintained for now.

The method (a) can be used per se, at least on Debian GNU/Linux, or
within chroot or LXC environments.

Unfortunately, the Python extensions are coupled with the rest of the
Coriolis, so it is impossible to use the advantages of 'virtualenv' or
similar environments with Coriolis.

Thus, entering the development with Coriolis for pythonistas is
complicated by the combination of two factors:

- lack of native packages for their OSes,
- lack of PyPI package or pip/virtualenv support.

I understand that Coriolis is a niche product, so we can not really
expect much in terms of packaging for popular OSes. So it may be better
for Coriolis to take another route:

- decouple Python extensions from the main product,
- provide Python extensions as a pip package (via PyPI or git),
- supply a script and/or instructions for building the main product
with the pip package.

This is actually not a unique approach. For example, xapian-haystack
ships a script for building a whole Xapian search engine (C++) in
PYTHONPATH [3].

2. Documentation
.
All the basics are covered by Coriolis User's Guide [4] (general
workflow and GUI) and Python Tutorial [5], that are available online
and offline, in PDF and HTML formats.

Unfortunately, Coriolis Python API don't have its own reference guide.
There is a good reference on Hurricane C++ API [6] though. Since Python
API just copies the C++ API (which is a terrible desicion by itself,
see the explanation in 3.2), this reference alone has the great part of
both C++ and Python APIs covered. But other parts of the Python API
(most importantly, Etesian and Katana) stays undocumented beyond the
basics.

3. API

3.1. Supported Python versions

The Coriolis Python API is a Python 2 extension.

Python 2.7 was released in 2010, and it was meant to be the last 2.x
release back then. In the following years Python 2 had no new features
other than backports from Python 3. As of January 2020 Python 2 is
considered unsupported by PSF. [7]

Still clinging to outdated and abandoned language and not even having a
(publicly available, at least) transition plan seems a bit scary to me.

3.2. Best practices of Python APIs

To have a new API mimic the old API written in another programming
language seems like an excellent idea at first. You don't have to
design anything. Don't have to think of naming. You can reuse
documentation and tests. The new API is easy to use, if you already got
used to the old one. Everybody's happy, right?

Well, everybody except the end users whom the new API is created for.

Each programming language has its own best practices, and most of the
time they either contradict the ones accepted by another language users
or just don't have analogues in that language. Your new users will see
your API as alien, cumbersome, or just poorly designed. They may have
to cram their way around the least expected features. They may have to
write wrappers around your API to reduce the astonishment factor [8]
for the others. But most likely they will simply walk away.

Here I'll try to give a run-down of Coriolis API features that scares
Python developers (“bad”) along with their attractive and comfy
alternatives (“good”).

3.2.1. Singletons

You don't need a special methods to create and access a unique object
in Python, since you can just import it.

Bad: af = CRL.AllianceFramework.get()

Good: from CRL import af

3.2.2. Getters and setters

Getters and setters are considered an antipattern (not only in Python),
so they should be replaced by properties or collection-like interfaces.

Bad:
  env = af.getEnvironment()
  env.setCLOCK('^ck$|m_clock|^clk$')

Good:
  af.env['CLOCK'] = '^ck$|m_clock|^clk$'

3.2.3. Data types

Python use duck typing, so you should avoid any direct type indication
or querying in Python.

Bad: Cfg.getParamInt('katana.vTracksReservedLocal').setInt(6)

Good: Cfg['katana.vTracksReservedLocal'] = 6

3.2.4. Syntactic sugar

It's easier to account for the certain things that goes in pairs
(open/close, create/destroy) with context managers or decorators.

Bad:
  UpdateSession.open()
  do_my_thing()
  UpdateSession.close()

Good:
  with UpdateSession():
      do_my_thing()

Also good in some cases:
  @update_session
  def do_my_thing():
      ...

3.2.5. Self-documenting

Python have a built-in 'help()' function, that returns a docstring for
a given object. Python C extensions can emulate a docstring for use
with 'help()'. Static syntax checkers and IDEs also rely on this API.

It is very important that this emulated docstring contains not only the
description of the function or method, but also a signature (parameters
and return value) in reST format, as recommended by PEP287 [9], or in
older Epytext format at worst. This will greatly facilitate the use of
Python C extension with modern IDEs.

The rules have slightly changed since Python 3.4, but the idea remains.

3.2.6. Naming conventions

The Python API must adhere to naming conventions accepted in Python. I
can not stress enough the importance of this point, but let us address
the styling issues in general in 3.3.

3.3. Styling

I have to admit that Coriolis Python style is quite consistent, but it
looks like the only purpose of this consistency is to contradict the
PEP 8 [10] in any possible way. [11]

You might think that style is not that important, but after 15 minutes
spent in search of the 'ChipRoute' class definition, diagnosing and
restarting IDE, checking Moon phase and whatnot, find that 'ChipRoute' 
is not a class, but a module… How well the end user could perform with
that in mind?

Another thing is that it's nearly impossible to lure a junior developer
into a project that neglects styling. In modern development,
proprietary and opensource alike, an ability to write a consistent,
readable, uniform code is very much appreciated, and junior developers
expect to acquire good professional habits in their first projects. And
style is the first thing they learn to distinguish in someone else's
code.

[1] http://coriolis.lip6.fr/pages/users-guide.html#id16
[2] http://coriolis.lip6.fr/pages/users-guide.html#id19
[3] https://github.com/notanumber/xapian-haystack
[4] http://coriolis.lip6.fr/pages/users-guide.html
[5] http://coriolis.lip6.fr/pages/python-tutorial.html
[6] http://coriolis.lip6.fr/doc/hurricane/index.html
[7] https://www.python.org/dev/peps/pep-0373/
[8] https://en.wikipedia.org/wiki/Principle_of_least_astonishment
[9] https://www.python.org/dev/peps/pep-0287/
[10] https://www.python.org/dev/peps/pep-0008/
[11] 
https://www.opensourceshakespeare.org/views/plays/play_view.php?WorkID=hamlet&Act=2&Scene=2&Scope=scene&LineHighlight=1307#1307



_______________________________________________
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] another CDC6600 reference on IEEE
From: Luke Kenneth Casson Leighton @ 2020-03-28  6:07 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <cf736037e77c4433f1c9d1b8f6166bf7@f-cpu.org>

On Saturday, March 28, 2020, <whygee@f-cpu.org> wrote:

> Hi !
> I found this reference
> https://ieeexplore.ieee.org/document/4639400/
> I thought it might bring some insight about the scoreboard


read mitch's book chapters.


> but I can't read it -_-


 Date of Publication: Oct.-Dec. 1980

woow.




-- 
---
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] another CDC6600 reference on IEEE
From: whygee @ 2020-03-28  1:19 UTC (permalink / raw)
  To: Libre-RISCV General Development

Hi !
I found this reference
https://ieeexplore.ieee.org/document/4639400/
I thought it might bring some insight about the scoreboard
but I can't read it -_-

_______________________________________________
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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-27 21:36 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD42T0AhzAHcbCY+1YtuBMxvUnZuS=2PEu55UTHs-EbEJg@mail.gmail.com>

On Fri, Mar 27, 2020 at 9:31 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> Will add all the above stuff later, may have to delay till saturday night
> or sunday.

ok great.  no problem.

btw we need to start getting smart, work together, and get the
hardware (and simulator) operational with basic POWER integer
functionality, then LDs/STs (even if there's no efficient memory
read/write), then probably branches (with simple branch-prediction,
first).

i'm finding that i'm working well *with* people (poking in here and
there) such as you and michael (and Mitch, last year), however if i'm
doing something on my own - from scratch - i'm ridiculously slow.  two
weeks so far on the LD/ST buffer.  the IEEE754 work was an exception
because i had "something that worked" (the jondawson fpu) and could
rapidly morph it.

l.

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

* Re: [libre-riscv-dev] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-27 21:32 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7-bGgMQ2P6cWkYPDQNCsRKGVXP7rQCm4jvS4OFGVyVcw@mail.gmail.com>

On Fri, Mar 27, 2020 at 9:29 PM Jacob Lifshay <programmerjake@gmail.com> wrote:

> I haven't looked at the specific FP algorithms the Power spec specifies
> yet, but assuming they are like how IEEE 754 is specified, they specify it
> in terms of infinite-precision real numbers, which are not mappable to
> hardware without additional conversion to integer/fixed-point operations.

it appears to be bit-numbered sections of the incoming data.  like this:

If (FRB)1:11 < 897 and (FRB)1:63 > 0 then
     Do
         If FPSCRUE = 0 then goto Disabled Exponent Underflow
         If FPSCRUE = 1 then goto Enabled Exponent Underflow
     End

_______________________________________________
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] extremely busy crowdsupply update started
From: Jacob Lifshay @ 2020-03-27 21:31 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzjjQR-GtyRHoALd_MwV3J7vVmp-anbhxbzxbFJ7KkpNw@mail.gmail.com>

On Fri, Mar 27, 2020, 01:47 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Friday, March 27, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> >
> > I ended up with quite a bit more than a paragraph or two, hoping
> > that's ok since this is the first time simple-soft-float as appeared
> > in the CrowdSupply updates, and I've been working on it since june at
> > least. I'd appreciate a review by someone else to help catch errors. I
> > pushed my additions to crowdsupply.git.
>
>
> looks great jacob.
>
> were there any challenges or anything that was difficult or easy?  it is
> "insights" that are the kind of thing that make updates interesting.
>
> oh, do mention the "rust library of the month" thing for example, and when
> that happened, and how what has been done expands on that since.
>
> also i suggest explicitly mentioning that these two libraries can be used
> by *anyone*, they are *not* specific to this project, and are exactly the
> kind of side-benefit that comes from sponsorship from NLNet.  hm i might
> word that one if that's ok.
>
>
> oh, nearly forgot! can you also do a quick section on kazan, mentioning the
> intermediary milestone?
>

Will add all the above stuff later, may have to delay till saturday night
or sunday.

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] extremely busy crowdsupply update started
From: Jacob Lifshay @ 2020-03-27 21:29 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzdUCst63B3ZFh6jyqLexdq3SjmUstJ=n9dNY=pMT_HyA@mail.gmail.com>

On Fri, Mar 27, 2020, 12:21 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> FP is a little more challenging because they use "words" to describe
> most aspects of the hardware.  oh wait!  Appendix A p775 v3.0B
> contains FP to rounding algorithms, and a few more besides.
>
> i would not be at all surprised if, should we do document-parsing, we
> had an entire simulator for the integer V3.0 system in a week, and the
> hardware in around 2.


I haven't looked at the specific FP algorithms the Power spec specifies
yet, but assuming they are like how IEEE 754 is specified, they specify it
in terms of infinite-precision real numbers, which are not mappable to
hardware without additional conversion to integer/fixed-point operations.

Jacob

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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-27 19:21 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <9561ee2b-1b98-01f4-cdf0-a2879dd7f0bb@gmail.com>

On Fri, Mar 27, 2020 at 4:56 PM Michael Nolan <mtnolan2640@gmail.com> wrote:

> > * michael could you do something about the use of GNU as and qemu?
> Sure, I'll work on it at some point today or tomorrow.

star.

_______________________________________________
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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-27 19:20 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200327173545.2974f6c21ade7d9adfcc9808@platen-software.de>

On Fri, Mar 27, 2020 at 4:35 PM Tobias Platen
<libre-soc@platen-software.de> wrote:
>
> On Fri, 27 Mar 2020 15:49:45 +0000
> Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
>
> I've cloned the repository and now I could write something to fill one or more TODOs in the file 023_2020mar26_decoder_emulator_started.mdwn probably either Coriolis2 experimentation started or POWER ISA decoder and Simulator.

sure - i've added you to the repo so you can git push to it.

> I think I'll work on the POWER ISA decoder and Simulator next.

i had an idea about that, based on this:

http://lists.mailinglist.openpowerfoundation.org/pipermail/openpower-hdl-cores/2020-March/000007.html

my feeling is, we're wasting our time trying to "manually" create both
a processor and also a simulator, from "scratch", when there are
perfectly good, machine-readable expressions (at least for the integer
instructions), like this:

lbz         RT,D(RA)
    34      RT      RA     D
0        6       11     16   31
if RA = 0 then b <= 0
else           b <= (RA)
EA <= + EXTS(D)
RT <= 56^0 || MEM(EA, 1)

i'm advocating, therefore, that we *literally* parse the PDF spec,
create an "interpreter" for those fragments, then auto-generate code
and HDL from them.

mulhwu      RT,RA,RB                      (Rc=0)
mulhwu.     RT,RA,RB                      (Rc=1)
    31      RT      RA      RB    /    11    Rc
0        6       11      16      21 22       31

prod0:63 <- (RA)32:63 x (RB)32:63
RT32:63 <- prod0:31
RT0:31 <- undefined

those really don't look very hard, to turn into code, do they?

FP is a little more challenging because they use "words" to describe
most aspects of the hardware.  oh wait!  Appendix A p775 v3.0B
contains FP to rounding algorithms, and a few more besides.

i would not be at all surprised if, should we do document-parsing, we
had an entire simulator for the integer V3.0 system in a week, and the
hardware in around 2.

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] extremely busy crowdsupply update started
From: Michael Nolan @ 2020-03-27 16:56 UTC (permalink / raw)
  To: Luke Kenneth Casson Leighton, Libre-RISCV General Development,
	Jock Tanner, Immanuel, Yehowshua U
In-Reply-To: <CAPweEDw_h8VQ3JJFF3FXph7Eg0ucVknuvMk=Xc0jSp0WP13=UQ@mail.gmail.com>

On 3/26/20 5:03 PM, Luke Kenneth Casson Leighton wrote:
> https://git.libre-riscv.org/?p=crowdsupply.git;a=blob;f=updates/023_2020mar26_decoder_emulator_started.mdwn;hb=HEAD
>
> this is just the beginning, i have to fill in the sections - it would
> be really handy if people could help!
>
> * michael could you do something about the use of GNU as and qemu?
Sure, I'll work on it at some point today or tomorrow.

_______________________________________________
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] extremely busy crowdsupply update started
From: Tobias Platen @ 2020-03-27 16:35 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <CAPweEDx_9P+WK8Tk2RvY3gJW6WZ0_3-q1eRARjthrF1UMvYt6g@mail.gmail.com>

On Fri, 27 Mar 2020 15:49:45 +0000
Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

I've cloned the repository and now I could write something to fill one or more TODOs in the file 023_2020mar26_decoder_emulator_started.mdwn probably either Coriolis2 experimentation started or POWER ISA decoder and Simulator. I think I'll work on the POWER ISA decoder and Simulator next. 

> On Fri, Mar 27, 2020 at 2:39 PM Immanuel, Yehowshua U
> <yimmanuel3@gatech.edu> wrote:
> >
> > > * yehowshua if you could write a paragraph or two about CREATE-X
> >
> > Yes, let me get back to you later today.
> 
> thanks.  you are actually on the list for this repo so could git
> commit if you wanted to
> https://git.libre-riscv.org/?p=crowdsupply.git;a=summary
> 
> 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

* [libre-riscv-dev] [Bug 268] nmigen does not seem to support write-through SRAM
From: bugzilla-daemon @ 2020-03-27 16:05 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-268-13@http.bugs.libre-riscv.org/>

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
okaaay so that's write-port *priority*, not the same thing as write-*through*
capability.  you've got a (similar?) unit test kicking around, would you be ok
writing a similar one that checks if what is written can be read on the same
clock cycle?

-- 
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] extremely busy crowdsupply update started
From: Luke Kenneth Casson Leighton @ 2020-03-27 15:49 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <69A29B9F-05D0-4F41-B3F6-E8CC4FDDCE79@gatech.edu>

On Fri, Mar 27, 2020 at 2:39 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> > * yehowshua if you could write a paragraph or two about CREATE-X
>
> Yes, let me get back to you later today.

thanks.  you are actually on the list for this repo so could git
commit if you wanted to
https://git.libre-riscv.org/?p=crowdsupply.git;a=summary

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] extremely busy crowdsupply update started
From: Immanuel, Yehowshua U @ 2020-03-27 14:39 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDw_h8VQ3JJFF3FXph7Eg0ucVknuvMk=Xc0jSp0WP13=UQ@mail.gmail.com>

> * yehowshua if you could write a paragraph or two about CREATE-X

Yes, let me get back to you later today.

_______________________________________________
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: [llvm-dev] TTA-based Co-Design Environment (TCE) v1.21 Released
From: Jacob Lifshay @ 2020-03-27 14:18 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <c409803a-f9cb-4b6a-af78-80148b27233a@tuni.fi>

Seems interesting

---------- Forwarded message ---------
From: Pekka Jääskeläinen via llvm-dev <llvm-dev@lists.llvm.org>
Date: Fri, Mar 27, 2020, 06:31
Subject: [llvm-dev] TTA-based Co-Design Environment (TCE) v1.21 Released
To: llvm-dev <llvm-dev@lists.llvm.org>


TTA-based Co-Design Environment (TCE) is an open application-specific
instruction-set processor (ASIP) toolset for design and programming of
customized co-processors (compiler-programmable accelerators). It is
based on the energy efficient Transport Triggered Architecture (TTA)
processor template.

The toolset provides a complete retargetable co-design flow from high-
level language programs down to FPGA/ASIC synthesizable processor RTL
(VHDL and Verilog generation supported) and parallel program binaries.

The size and quantity of register files, function units, supported
operations, and the interconnection network can be freely customized to
create new co-processors ranging from small single-application specific
cores with special operations to static multi-issue domain-specific
processors.

Notable Changes
===============

This release adds support for LLVM 10, brings back an alias analyzer
for spill code, removes the need for 8b loads in a minimal machine,
and now allows having only one type of extension mode in loads.

Download
========

Get the release via git by cloning the release branch:

   git clone -b release-1.21 https://github.com/cpc/tce.git tce-1.21

Acknowledgements
================

The Customized Parallel Computing research group of Tampere University,
Finland did most of their work to this release as part of the FitOptiVis
project funded by ECSEL Joint Undertaking under grant number
H2020-ECSEL-2017-2-783162. Further support was received from HSA
Foundation. The financial support is very much appreciated!

Links
=====

TCE download page:  http://openasip.org/download.html
This announcement:  http://openasip.org/downloads/ANNOUNCEMENT
Change log:         http://openasip.org/downloads/CHANGES
Install info:       http://openasip.org/downloads/INSTALL

-- 
Pekka
_______________________________________________
LLVM Developers mailing list
llvm-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-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 268] nmigen does not seem to support write-through SRAM
From: bugzilla-daemon @ 2020-03-27 13:45 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-268-13@http.bugs.libre-riscv.org/>

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

--- Comment #3 from Jacob Lifshay <programmerjake@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #2)
> i think this was the basis of a unit test that jacob wrote, and he found that
> there was a definite bug in the nmigen Simulation.  i believe however it
> was a 2R1W arrangement.  jacob can you remember?

Found it:
https://salsa.debian.org/Kazan-team/simple-barrel-processor/-/blob/391d95f30bd99e37236af8fb95565809b7230e29/test/test_mem.py

nmigen bug:
https://github.com/m-labs/nmigen/issues/47

Turned out that write conflicts weren't implemented as advertised, the buggy
feature (write port priority) was later removed:
https://github.com/m-labs/nmigen/commit/a02e3750bfeba44bcaad4c5de8d9eb0ef055d9c6

-- 
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] cache SRAM organisation
From: Luke Kenneth Casson Leighton @ 2020-03-27 10:59 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <9e44930a0332eff507661e617796b9d0674b0e05.camel@fibraservi.eu>

On Fri, Mar 27, 2020 at 10:36 AM Staf Verhaegen <staf@fibraservi.eu> wrote:

> Yes and no, it is the basic functionality of a pipeline :(

yes.

> You have the same latency but can have double the number of operations in flight.

yes.  hence why it is so important to have, because double the number
of operations means that we need double the number of Function Units
in the Dependency Matrix in order to keep the entire out-of-order
engine occupied.

also, double the number of operations in flight means that we need
double the number of Branch Prediction Units, and much more complex
BPUs at that, just to deal with the (now very likely) scenario of
having far more overlapping inner loops "in flight".

all this from just extending the pipeline length(s) from 5 to 10.  so
it's not just a "nice-to-have" feature, it's actually really important
to keeping the overall size of the chip down.

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 268] nmigen does not seem to support write-through SRAM
From: bugzilla-daemon @ 2020-03-27 10:55 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-268-13@http.bugs.libre-riscv.org/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |programmerjake@gmail.com

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
i think this was the basis of a unit test that jacob wrote, and he found that
there was a definite bug in the nmigen Simulation.  i believe however it
was a 2R1W arrangement.  jacob can you remember?

-- 
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 268] nmigen does not seem to support write-through SRAM
From: bugzilla-daemon @ 2020-03-27 10:44 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-268-13@http.bugs.libre-riscv.org/>

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

Staf Verhaegen <staf@fibraservi.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |staf@fibraservi.eu

--- Comment #1 from Staf Verhaegen <staf@fibraservi.eu> ---
I may have overlooked something and write-through may actually be implemented.
I think the trick is to have both a read and a write port; have these port
share the same address signal and also do a read when you do a write (e.g. have
transparent read port which make the read port always enabled).

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

^ permalink raw reply

page:   latest

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

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

Example config snippet for mirrors


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