From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] PPC on Talos and Playstation 3
Date: Mon, 30 Mar 2020 22:02:44 +0000
Message-ID: <CAPweEDxq-2ReMzjxPnmFrXmKWegGZ35Qnx=wdGQYJNinXGmp4Q@mail.gmail.com> (raw)
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
next prev parent reply index
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 20:17 Immanuel, Yehowshua U
2020-03-29 20:20 ` Immanuel, Yehowshua U
2020-03-29 20:35 ` Jacob Lifshay
2020-03-29 21:01 ` Luke Kenneth Casson Leighton
2020-03-30 6:56 ` Lauri Kasanen
2020-03-30 7:12 ` Jacob Lifshay
2020-03-30 7:32 ` Lauri Kasanen
2020-03-30 7:52 ` Jacob Lifshay
2020-03-30 8:05 ` Lauri Kasanen
2020-03-30 18:07 ` Jacob Lifshay
2020-03-30 18:12 ` Immanuel, Yehowshua U
2020-03-30 18:16 ` Jacob Lifshay
2020-03-30 18:35 ` Immanuel, Yehowshua U
2020-03-30 18:36 ` Immanuel, Yehowshua U
2020-03-30 18:46 ` Luke Kenneth Casson Leighton
2020-03-30 18:57 ` Immanuel, Yehowshua U
2020-03-30 19:09 ` Luke Kenneth Casson Leighton
2020-03-30 19:20 ` Immanuel, Yehowshua U
2020-03-30 19:25 ` Luke Kenneth Casson Leighton
2020-03-30 19:35 ` Immanuel, Yehowshua U
2020-03-30 19:45 ` Jacob Lifshay
2020-03-30 19:46 ` Immanuel, Yehowshua U
2020-03-30 22:02 ` Luke Kenneth Casson Leighton [this message]
2020-03-30 19:01 ` Jacob Lifshay
2020-03-30 19:20 ` Luke Kenneth Casson Leighton
2020-03-31 21:57 ` Michael Nolan
2020-03-31 23:01 ` Luke Kenneth Casson Leighton
2020-04-01 0:23 ` Immanuel, Yehowshua U
2020-04-01 0:44 ` [libre-riscv-dev] additional ddr3 interfaces Jacob Lifshay
2020-04-01 0:47 ` Immanuel, Yehowshua U
2020-04-01 1:01 ` Jacob Lifshay
2020-04-01 11:10 ` Luke Kenneth Casson Leighton
2020-04-01 15:19 ` Staf Verhaegen
2020-04-01 15:42 ` Luke Kenneth Casson Leighton
2020-04-01 11:00 ` [libre-riscv-dev] PPC on Talos and Playstation 3 Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDxq-2ReMzjxPnmFrXmKWegGZ35Qnx=wdGQYJNinXGmp4Q@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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