Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
* Re: [libre-riscv-dev] PPC on Talos and Playstation 3
From: Luke Kenneth Casson Leighton @ 2020-03-30 22:02 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <927534AC-082A-46D0-B2E1-111552EDFC93@gatech.edu>

On Mon, Mar 30, 2020 at 8:35 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
> optional.  however we'll need to add our own modes: Khronos / Vulkan Compliance.
>
> Ah. Gotcha. So do we even NEED to test on ppc64?

yes absolutely.  otherwise, how will we know - for sure - that the HDL
is properly - and fully - ppc64 compliant?

> You can test 754 compliance on most anything.

except for PPC rounding modes and exception handling.  except that
IEEE754 compliance is *NOT* fully and exactly defined.  different
architectures have entirely different rules for rounding modes,
entirely different rules for NaN, and entirely different rules about
what and whether exceptions should be raised.


> If we opt out of the ppc mode -

ah no.  we absolutely have to have compliance with the requirements
set by the OpenPOWER Foundation.  otherwise we are not legally
permitted to use the name "POWER" associated with the project.

> then I imagine we don’t need PPC specific testing for the FPU.
> Is it possible to invoke PPC FPU mode through the instruction set?

it has to be enabled "by default".

we're negotiating with the OpenPOWER Foundation for the right to also
have a *Khronos* (Vulkan) Compliance Mode (as explained here:
https://libre-riscv.org/openpower/isans_letter/)

the fact that the "non IEEE mode" exists at all on POWER is a good sign.

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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-30 19:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5BSp8Xz6-BHCSKaA3-4w4Ep_v2SqbKNt8rsFwczrU29g@mail.gmail.com>

> We still have to implement all the extra status flags that Power defines,

Makes sense to me!

_______________________________________________
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] PPC on Talos and Playstation 3
From: Jacob Lifshay @ 2020-03-30 19:45 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <927534AC-082A-46D0-B2E1-111552EDFC93@gatech.edu>

On Mon, Mar 30, 2020, 12:35 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

>
> optional.  however we'll need to add our own modes: Khronos / Vulkan
> Compliance.
>
> Ah. Gotcha. So do we even NEED to test on ppc64?
> You can test 754 compliance on most anything.
>
> If we opt out of the ppc mode - then I imagine we don’t need PPC specific
> testing for the FPU.
> Is it possible to invoke PPC FPU mode through the instruction set?
>

We still have to implement all the extra status flags that Power defines,
since they are still used even in IEEE 754 compliant mode.

What needs testing is making sure simple-soft-float calculates all the
Power-specific status flags correctly, so I will be creating a bunch of
test cases on PPC hardware such that all the test cases can then be run on
any computer including x86. The HDL can then be designed to match
simple-soft-float without requiring PPC hardware to run any tests because
simple-soft-float will be verified to be correct.

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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-30 19:35 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzJ8bxDyPbpQp9_fSjD0_duqxmbeVGCpN4zxM-sM5OSwA@mail.gmail.com>


optional.  however we'll need to add our own modes: Khronos / Vulkan Compliance.

Ah. Gotcha. So do we even NEED to test on ppc64?
You can test 754 compliance on most anything.

If we opt out of the ppc mode - then I imagine we don’t need PPC specific testing for the FPU.
Is it possible to invoke PPC FPU mode through the instruction set?

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] Building Docker Containers
From: Cole Poirier @ 2020-03-30 19:31 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzzC2DrfUJN=CKrbrVxe2H2_by+18YGhUNoxYWEbkAmDQ@mail.gmail.com>



> On Mar 30, 2020, at 11:58 AM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> 
> On Mon, Mar 30, 2020 at 7:43 PM Cole Poirier <colepoirier@gmail.com> wrote:
> 
>> Don’t worry I kept my ssh keys. But I was having additional problems
>> that I believe were self-inflicted through careless pollution of my global
>> package namespace among other things, so I wanted to do a clean
>> install so that I don’t have erroneous bugs crop up due to this during
>> the HDL workflow setup.
> 
> don't do it!  teach yourself where things live, and how to find them,
> and how to safely remove them, rather than assuming that it's ok to
> blow away a box like it's a "toy Windoze machine" ok?
> 
> because you ain't doing that to a server, i can tell you that *right*
> now!  if people are depending on a server to be up, you are *not*
> going to be able to quotes blow it away quotes.
> 
> i managed once to overwrite the contents of /sbin and /usr/sbin and
> other places, once, on an x86 system by unpacking a cpio-formatted ARM
> initrd on it (cpio unpacks to *absolute* paths by default...)
> 
> i absolutely was *not* going to quotes reinstall it quotes because it
> was a mac, which at the time was a f*****g nuisance to put UEFI
> bootable linux on it.  so i rescued it by mounting then chrooting into
> a live bootable install disk, unpacking some of the relevant .deb
> archives (by hand) and manually copying files over, one by one.

Don’t worry, I would never think to do this to a server, let alone one of 
yours, Jacob’s, someone else’s, or another libre-soc server. Unfortunately,
I already have done this to my local pc, but I don’t plan on doing this again. 
I had spent the past week doing the manual investigation and recovery 
method and was still encountering transient bugs and problems. If this 
were a server I would have—preferably not have been so careless 
in the first place, but barring this—continued on in my debugging, and 
reached out to the list for help if I was still unable to solve the issues 
after a second concerted effort. This is the procedure I will follow should
I unfortunately find myself with a buggy OS in the future, however I am 
planning to be much more careful and mindful about my installations 
and configurations moving forward. 

> 
>> It was my mistaken assumption that changing
>> my username would interfere with the proper functioning of my ssh
>> key because it has my old username instead of my new one. I’m happy
>> I was wrong :)
> 
> yes.  ssh keys have absolutely nothing to do with usernames.
> 
> l.

Good to know, thank you very much!

Cole


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

^ permalink raw reply

* Re: [libre-riscv-dev] PPC on Talos and Playstation 3
From: Luke Kenneth Casson Leighton @ 2020-03-30 19:25 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <14D10491-B154-4613-B3AA-50DC1C0362A8@gatech.edu>

On Mon, Mar 30, 2020 at 8:20 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:

> Ok. Cool. Also, I’m guessing we still have to support POWER’s non-IEEE mode?

optional.  however we'll need to add our own modes: Khronos / Vulkan Compliance.

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 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-30 19:24 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>

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

--- Comment #2 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #1)
> Would this be in power_pseudo.py? Or the POC simulator I wrote?

in the simulator, as a base "convenience" class of some kind.

basically, right now, code like this (which is extswsli)

    n  <- sh[5] || sh[0:4]
    r  <- ROTL64(EXTS64(RS[32:63]), n)
    m  <- MASK(0, 63-n)
    RA <- r & m

currently gets turned into this:

    n  = sh[5] + sh[0:5] # these are lists so they get concatenated
    r  = ROTL64(EXTS64(RS[32:64]), n)
    m  = MASK(0, 63-n)
    RA = r & m

however what is *actually* needed is:

    n  = sh[5] + sh[0:5] # these are lists so they get concatenated
    r  = self.helperfns.ROTL64(self.helperfns.EXTS64(RS[32:64]), n)
    m  = self.helperfns.MASK(0, 63-n)
    RA = r & m

and some other small changes.

remember, the code that's being executed will be *in* the simulator.
it's only generated *by* the compiler (power_pseudo.py).

welcome to compilers, they're a bit of a mind-bender :)

-- 
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] PPC on Talos and Playstation 3
From: Luke Kenneth Casson Leighton @ 2020-03-30 19:20 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5Etbih+gzJWpseB5mTMtKXLTFhgsbstPVXoPEy00jBXA@mail.gmail.com>

On Mon, Mar 30, 2020 at 8:01 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Mon, Mar 30, 2020, 11:36 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
> wrote:
>
> > Before I try my hand at an FPU,
> >
> > Some questions:
> >  - Do we have any FPU attempt in nMigen, Verilog, or some other language
> > yet that I should be aware of?
> >
>
> yes, https://git.libre-riscv.org/?p=ieee754fpu.git;a=summary

sorry, missed this question.  yehowshua: we have a *95% completed*
IEEE754 FPU already.  we don't need another one.  we _do_ however need
a formal proof of the one that we already have, plus adding POWER
rounding modes to the one that we already have.

> I was assuming we'd just implement them both as fully IEEE 754 compliant,
> unless the noncompliant mode mandates something incompatible with IEEE 754
> such as flushing denormals to zero.

have to check.  i wasn't aware the mode existed until 5 minutes ago.  3.0B p126

bit 61:

Floating-Point Non-IEEE Mode (NI)
Floating-point non-IEEE mode is optional. If
floating-point non-IEEE mode is not imple-
mented, this bit is treated as reserved, and the
remainder of the definition of this bit does not
apply.
If floating-point non-IEEE mode is imple-
mented, this bit has the following meaning.
0 The processor is not in floating-point
     non-IEEE mode (i.e., all floating-point
     operations conform to the IEEE standard).
1 The processor is in floating-point
     non-IEEE mode.

so it's optional, thank goodness.

> 4x16-bit, 2x32-bit, 64-bit. We're planning on having 2 64-bit units. The
> FPU should be designed to reuse the reconfigurable integer multiplier since
> that's most of the logic in fpmul or fma.

yes.  this means:

* splitting the FPU pipeline into pre- and post- processing pipelines
* feeding the (partial) results from the FP pre-processing pipeline *back*
  into (side-channel, non-Dependency-tracked) Function Units
* those request an InternalOp "MUL" (integer MUL) and mark the results
  as belonging to an FP operation
* such that when the INT MUL finishes, the results get pushed back
  to the Function Units again, now into the FINAL stage..
* which is to perform the FPU post-processing pipeline

so the data goes THREE TIMEs through the Function Units, going through
THREE separate pipelines.

> Also, the FP divider should also be shared with integer div/rem.

... and therefore the exact same trick as above will be needed.

interestingly this means that, hypothetically, we can do integer SQRT
and ineger RSQRT.  the hardware exists: it's just that there's no
opcodes in POWER to get access to them.

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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-30 19:20 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDxQGsJqQYq=KwMzV3MGUCh-6zPPpgK+eh3cNxMUbRO-jw@mail.gmail.com>



On Mar 30, 2020, at 3:09 PM, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:

> we still have to do SIN, COS, ATAN2, ROOT3, POW, LOG, LOG1P, ACOS and
> more.  this will be about another 2 months.

Ok. Cool. Also, I’m guessing we still have to support POWER’s non-IEEE mode?

It looks like all we’ve got is 754 support at the moment..

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] PPC on Talos and Playstation 3
From: Luke Kenneth Casson Leighton @ 2020-03-30 19:09 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <84B46705-7450-49CD-924B-72170B8693A4@gatech.edu>

On Mon, Mar 30, 2020 at 7:57 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:
>
> > yehowshua, you're aware that by choosing to do this, that you'll be
> > committing over 6 months of your life to the task?  that's typically
> > how long it takes (if not longer).
>
> Oh wow! Why so long

https://git.libre-riscv.org/?p=ieee754fpu.git;a=shortlog;pg=19
then page back and watch the months go by.

> - I was thinking maybe 4 weeks…

no chance.  we started in february, last year, working from jon
dawson's verilog code and hand-converting it to nmigen.  we were
delighted when, a week later, we had working IEEE754 FP add.

by around 2 months we had MUL and a decent pipeline structure.  at
some point i worked out how to parameterise the code.

at least 6 weeks were spent writing unit tests.

FPDIV took about 2 months: Jacob wrote some code that does div *and*
sqrt *and* rsqrt, that was about 5 weeks i think?  then it took me
about 3 weeks to join it together into FP (jacob's code was
fixed-integer).

then i added integer to fp and fp to integer, and class and FCVT,
those all took around... 2 and a half weeks i think, including unit
tests.

michael recently did FPMAX, FPCMP etc. which was... about a week.

we still have to do SIN, COS, ATAN2, ROOT3, POW, LOG, LOG1P, ACOS and
more.  this will be about another 2 months.


> At a minimum, I’d like to at least see how well Bluespec handles FPU configuration.

great - just remember that we're under time pressure and so anything
that means "team has to learn a new language which is KNOWN to cause
massive problems due to its insanely high barrier to entry" has to be
excluded from going into the ASIC.

> The maintainer of BSC has been quite helpful in general - so I should him or her just how flexible is BSC for specifying an FPU…

is that Niraj?  he's really good.

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] Building Docker Containers
From: Jacob Lifshay @ 2020-03-30 19:08 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDzzC2DrfUJN=CKrbrVxe2H2_by+18YGhUNoxYWEbkAmDQ@mail.gmail.com>

On Mon, Mar 30, 2020, 11:59 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> On Mon, Mar 30, 2020 at 7:43 PM Cole Poirier <colepoirier@gmail.com>
> wrote:
> > It was my mistaken assumption that changing
> > my username would interfere with the proper functioning of my ssh
> > key because it has my old username instead of my new one. I’m happy
> > I was wrong :)
>
> yes.  ssh keys have absolutely nothing to do with usernames.
>

The field in the ssh key that looks like a username is actually the comment
field, you can put anything you like there (by using one of the options for
ssh-keygen to properly edit the files), though I'm not sure if it would
need to be updated on our servers if you change the comment field. I
recommend just leaving it.

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 272] functions needed in POWER simulator which match 3.0B spec
From: bugzilla-daemon @ 2020-03-30 19:04 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-272-13@http.bugs.libre-riscv.org/>

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

--- Comment #1 from Michael Nolan <mtnolan2640@gmail.com> ---
Would this be in power_pseudo.py? Or the POC simulator I wrote?

-- 
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] PPC on Talos and Playstation 3
From: Jacob Lifshay @ 2020-03-30 19:01 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <32516E1C-2A42-4C24-8E67-B8FB051DDD44@gatech.edu>

On Mon, Mar 30, 2020, 11:36 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> Before I try my hand at an FPU,
>
> Some questions:
>  - Do we have any FPU attempt in nMigen, Verilog, or some other language
> yet that I should be aware of?
>

yes, https://git.libre-riscv.org/?p=ieee754fpu.git;a=summary

 - The POWER ISA 3.0 PDF doc specifies an IEEE 745-1985 compliant mode as
> well as a faster non-compliant mode - I’m guessing we have to implement
> both?
>

I was assuming we'd just implement them both as fully IEEE 754 compliant,
unless the noncompliant mode mandates something incompatible with IEEE 754
such as flushing denormals to zero.

 - I imagine your RUST algebraics library should be useful for this?
>

Assuming you mean simple-soft-float, since algebraics is basically a exact
real number arithmetic library rather than a IEEE 754 library.
I hope so, i'm currently adding support for power-specific status flags and
proper NaN payload propagation, which are the last two things needed to be
fully Power compliant (assuming no bugs). It is currently RISC-V compliant
since RISC-V doesn't have extra status flags or NaN payload propagation.

 - how many stages should I have for the FPU - is there a sweetspot?
>

for add/sub/mul, somewhere around 3 or 4, for div/sqrt/recip-sqrt more is
ok, maybe 8-10?

 - We’re doing a reconfigureable FPU correct? What bit modes does it
> support?
>

4x16-bit, 2x32-bit, 64-bit. We're planning on having 2 64-bit units. The
FPU should be designed to reuse the reconfigurable integer multiplier since
that's most of the logic in fpmul or fma.

Also, the FP divider should also be shared with integer div/rem. For a
working pipelined integer/fixed-point div/rem/sqrt/recip-sqrt unit, see:
https://git.libre-riscv.org/?p=ieee754fpu.git;a=tree;f=src/ieee754/div_rem_sqrt_rsqrt;h=f00513f47bd2a839de0ac79c578fd94d1b73e6b3;hb=HEAD


> Yehowshua
>
> _______________________________________________
> 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] Building Docker Containers
From: Luke Kenneth Casson Leighton @ 2020-03-30 18:58 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <A1006D58-F26C-476F-8170-04E9BDAE2871@gmail.com>

On Mon, Mar 30, 2020 at 7:43 PM Cole Poirier <colepoirier@gmail.com> wrote:

> Don’t worry I kept my ssh keys. But I was having additional problems
> that I believe were self-inflicted through careless pollution of my global
> package namespace among other things, so I wanted to do a clean
> install so that I don’t have erroneous bugs crop up due to this during
> the HDL workflow setup.

don't do it!  teach yourself where things live, and how to find them,
and how to safely remove them, rather than assuming that it's ok to
blow away a box like it's a "toy Windoze machine" ok?

because you ain't doing that to a server, i can tell you that *right*
now!  if people are depending on a server to be up, you are *not*
going to be able to quotes blow it away quotes.

i managed once to overwrite the contents of /sbin and /usr/sbin and
other places, once, on an x86 system by unpacking a cpio-formatted ARM
initrd on it (cpio unpacks to *absolute* paths by default...)

i absolutely was *not* going to quotes reinstall it quotes because it
was a mac, which at the time was a f*****g nuisance to put UEFI
bootable linux on it.  so i rescued it by mounting then chrooting into
a live bootable install disk, unpacking some of the relevant .deb
archives (by hand) and manually copying files over, one by one.


> It was my mistaken assumption that changing
> my username would interfere with the proper functioning of my ssh
> key because it has my old username instead of my new one. I’m happy
> I was wrong :)

yes.  ssh keys have absolutely nothing to do with usernames.

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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-30 18:57 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDwbqrhvK-CwCSA7NJemMSAyhjhyXLQQQay=3wQPJaTrAA@mail.gmail.com>

> yehowshua, you're aware that by choosing to do this, that you'll be
> committing over 6 months of your life to the task?  that's typically
> how long it takes (if not longer).

Oh wow! Why so long - I was thinking maybe 4 weeks…

At a minimum, I’d like to at least see how well Bluespec handles FPU configuration.
The maintainer of BSC has been quite helpful in general - so I should him or her just how flexible is BSC for specifying an FPU…

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] PPC on Talos and Playstation 3
From: Luke Kenneth Casson Leighton @ 2020-03-30 18:46 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <32516E1C-2A42-4C24-8E67-B8FB051DDD44@gatech.edu>

On Mon, Mar 30, 2020 at 7:35 PM Immanuel, Yehowshua U
<yimmanuel3@gatech.edu> wrote:

> Before I try my hand at an FPU,

yehowshua, you're aware that by choosing to do this, that you'll be
committing over 6 months of your life to the task?  that's typically
how long it takes (if not longer).

> Some questions:
>  - Do we have any FPU attempt in nMigen, Verilog, or some other language yet that I should be aware of?
>  - The POWER ISA 3.0 PDF doc specifies an IEEE 745-1985 compliant mode as well as a faster non-compliant mode - I’m guessing we have to implement both?

sigh.  probably.

>  - how many stages should I have for the FPU - is there a sweetspot?

we have a trade-off between maximum clock rate and the number of
Function Units (Reservation Stations) needed.  so if there are 16-long
pipelines, then that *REQUIRES* 16 Function Units, in order to keep
them fully occupied and still be able to re-associate the result with
the correct FU when it comes back out the pipeline.

if the number of FUs increases too much, we have a problem with the
size of the Dependency Matrices.

i really do not want to go above around 20 FUs.  that's still pushing it.

* 6 to 8 of those will be LOAD/STORE.
* at least 2 will be Branch.
* at least 2 will be for predication.

this only leaves 8 (EIGHT!) for ALU operations, which in turn means
that pipelines really cannot go about 8 stages, and that we cannot
have separate FP and INT Function Units.


>  - We’re doing a reconfigureable FPU correct? What bit modes does it support?

literally anything.  it's defined in a single python dictionary, with
the mantissa and exponent being specified as parameters, by way of a
lookup (the bitwidth) as the key of the python dictionary.

one line of code.

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] Building Docker Containers
From: Cole Poirier @ 2020-03-30 18:43 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7tV2VA=OV1-9HrniE4LF5wxvSnDF4k0NscmGfVYzP4cA@mail.gmail.com>

> On Mar 30, 2020, at 11:13 AM, Jacob Lifshay <programmerjake@gmail.com> wrote:
> 
> On Mon, Mar 30, 2020, 01:59 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> wrote:
> 
>> yes... except bear in mind that you in no way need to do a "Windows".
>> 
>> 1. git --global user.name blah
>> 2. git --global user.email blah
>> 3. sudo bash
>> 4. mv /home/blah /home/blahblah
>> 5. edit /etc/passwd /etc/shadow and /etc/group
>> 
> 
> don't forget /etc/gshadow
> 
> Jacob

Don’t worry I kept my ssh keys. But I was having additional problems
that I believe were self-inflicted through careless pollution of my global
package namespace among other things, so I wanted to do a clean
install so that I don’t have erroneous bugs crop up due to this during 
the HDL workflow setup. It was my mistaken assumption that changing 
my username would interfere with the proper functioning of my ssh
key because it has my old username instead of my new one. I’m happy
I was wrong :)

Cole


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

^ permalink raw reply

* Re: [libre-riscv-dev] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-30 18:36 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <32516E1C-2A42-4C24-8E67-B8FB051DDD44@gatech.edu>

I see this:

https://salsa.debian.org/Kazan-team/simple-soft-float

But it looks like no HDL so far…

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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-30 18:35 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD5MvUYL=tzv0XFKt8ewv2FAOihmEQta5yzHwxxR7ewZzA@mail.gmail.com>

Before I try my hand at an FPU,

Some questions:
 - Do we have any FPU attempt in nMigen, Verilog, or some other language yet that I should be aware of?
 - The POWER ISA 3.0 PDF doc specifies an IEEE 745-1985 compliant mode as well as a faster non-compliant mode - I’m guessing we have to implement both?
 - I imagine your RUST algebraics library should be useful for this?
 - how many stages should I have for the FPU - is there a sweetspot?
 - We’re doing a reconfigureable FPU correct? What bit modes does it support?

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] PPC on Talos and Playstation 3
From: Jacob Lifshay @ 2020-03-30 18:16 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <74204B73-57B3-4842-9072-C2854C128D62@gatech.edu>

On Mon, Mar 30, 2020, 11:13 Immanuel, Yehowshua U <yimmanuel3@gatech.edu>
wrote:

> @Jacon - If I can manipulate 64bit floats on my 32 bit ppc Mac - is that
> acceptable for testing the FPU?
>

Assuming you meant @Jacob.

32-bit ppc should be sufficient for just testing the FPU if you already
have the hardware, but 64-bit ppc64 is preferred.

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] Building Docker Containers
From: Jacob Lifshay @ 2020-03-30 18:13 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAPweEDyxstZhnKLtE1T_HCJCtitCMOOMWpNb_Na_5B3vjmum6A@mail.gmail.com>

On Mon, Mar 30, 2020, 01:59 Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:

> yes... except bear in mind that you in no way need to do a "Windows".
>
> 1. git --global user.name blah
> 2. git --global user.email blah
> 3. sudo bash
> 4. mv /home/blah /home/blahblah
> 5. edit /etc/passwd /etc/shadow and /etc/group
>

don't forget /etc/gshadow

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] PPC on Talos and Playstation 3
From: Immanuel, Yehowshua U @ 2020-03-30 18:12 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <CAC2bXD7+uUdhEm1tKwwfttXsFO_Bs26E9YoMr8DM2vXH2tTDYA@mail.gmail.com>

@Jacon - If I can manipulate 64bit floats on my 32 bit ppc Mac - is that acceptable for testing the FPU?

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] PPC on Talos and Playstation 3
From: Jacob Lifshay @ 2020-03-30 18:07 UTC (permalink / raw)
  To: Libre-RISCV General Development
In-Reply-To: <20200330110511.ce0aea5ac7aaaab251b73aa3@gmx.com>

On Mon, Mar 30, 2020, 01:04 Lauri Kasanen <cand@gmx.com> wrote:

> On Mon, 30 Mar 2020 00:52:31 -0700
> Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> > Normally, the size of a pointer or general-purpose integer register is
> used
> > to determine 32 or 64-bit rather than the size of the FP unit since
> nearly
> > every processor more powerful than a microcontroller supports 64-bit FP.
> > even the 8086 (16-bit) supports 64-bit floating point (or even 80-bit)
> with
> > the 8087 math coprocessor. Also, recent intel processors support 512-bit
> FP
> > registers (the avx512 instruction set), but it's only a 64-bit processor.
>
> Aiye, but the context was running 64-bit fpu code, and with an embedded
> cpu it's possible it would not have such.
>

yeah, I guess.

Sorry if I sound overly negative.

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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 18:03 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>

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

--- Comment #12 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Luke Kenneth Casson Leighton from comment #11)

> be necessary... *as long* as we refer to those fields.

correction: sub-signals.

-- 
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 271] SigDecode in power_fields has extra spurious fields
From: bugzilla-daemon @ 2020-03-30 18:03 UTC (permalink / raw)
  To: libre-riscv-dev
In-Reply-To: <bug-271-13@http.bugs.libre-riscv.org/>

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

--- Comment #11 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Michael Nolan from comment #9)
> Interesting, it looks like we're going to need to remove the [0:-1] from
> anything that uses the fields now.

it was a bad hack, i couldn't work out how to just refer to the field
without going through __getattr__.

now that everything goes *through* the equivalent of that, and is now
sub-signals (slices of the original opcode), yes that hack should not
be necessary... *as long* as we refer to those fields.

-- 
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