Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] PowerISA 3.1 (Power10) spec released
Date: Mon, 11 May 2020 23:27:38 -0700
Message-ID: <CAC2bXD68V1G5Rd5U0xBYHduNHJsZECMU_EiGbQpjnWQT9Y1ncQ@mail.gmail.com> (raw)
In-Reply-To: <20200512090144.8fe5608fc7b63c8b6b33367a@gmx.com>

On Mon, May 11, 2020, 23:01 Lauri Kasanen <cand@gmx.com> wrote:

> Hi,
>
> The thing that stood out to me in the levels was BE/LE. An int or float
> compatible Power processor must support BE, LE is optional at those
> levels. A Linux level processor must support LE, BE is optional at that
> level. However the Linux level requires SIMD.
>
> So this means that our int+float processor must support BE.


not necessarily, it defines 4 compatibility levels, notice that all
features included in higher levels are not forbidden in lower levels, so we
could claim to be 100% compatible with the lowest level and we could still
implement nearly everything from higher levels, we just couldn't claim to
implement the named int+fp level. We could still claim to implement fp
instructions (assuming we actually do) and to be totally compatible with
LE-only int+fp (which we should probably ask OpenPower to add as a
supported level).

Note that the levels aren't strictly subsets of each other, so they're more
like named feature sets rather than levels.

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

  reply index

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 17:34 Lauri Kasanen
2020-05-11 18:25 ` Luke Kenneth Casson Leighton
2020-05-11 18:28   ` Luke Kenneth Casson Leighton
2020-05-11 18:31   ` Yehowshua
2020-05-11 18:37     ` Luke Kenneth Casson Leighton
2020-05-12  6:01 ` Lauri Kasanen
2020-05-12  6:27   ` Jacob Lifshay [this message]
2020-05-12  6:44     ` Lauri Kasanen
2020-05-12  7:06       ` Jacob Lifshay
2020-05-12  7:56         ` Luke Kenneth Casson Leighton
2020-05-12 13:55           ` Hendrik Boom
2020-05-12 14:46             ` Luke Kenneth Casson Leighton
2020-05-12 15:11               ` Hendrik Boom
2020-05-12 15:56                 ` Luke Kenneth Casson Leighton
2020-05-12  7:36   ` Luke Kenneth Casson Leighton
2020-05-12  7:50   ` Luke Kenneth Casson Leighton
2020-05-12  8:23     ` Lauri Kasanen
2020-05-12  8:33       ` Luke Kenneth Casson Leighton
2020-05-12  8:50         ` Lauri Kasanen
2020-05-12  9:09           ` 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=CAC2bXD68V1G5Rd5U0xBYHduNHJsZECMU_EiGbQpjnWQT9Y1ncQ@mail.gmail.com \
    --to=programmerjake@gmail.com \
    --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