[libre-riscv-dev] berkeley-softfloat-3 implements different variants of IEEE754

[Luke Kenneth Casson Leighton]

On Thursday, February 28, 2019, Hendrik Boom <hendrik at topoi.pooq.com> wrote:

>
> > either way, we have to choose:
> >
> > * do we implement RISC-V *only*
> > * do we implement an option to comply with x86 variations on the
> > IEEE754 standard
> >
> > in particular this makes testing complex: you actually have to compile
> > *special versions* of sfpy with -DSPECIALIZE_TYPE=RISCV (or other
> > variant).
>
> Seems to me that if we are implementing a RISC-V we should follow the
> RISC-V spec.
>
> Or is there some reason to do otherwise?


The library is intended to be general purpose. RISCV is a specialisation


>
> Perhaps to make it easy to write x86 emulators on the RISC-V?


Or ARM emulators running on x86 and so on


> Or is the RISC-V convention a violation of the IEEE arithmetic spec?
>
>

Honestly don't know





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