On Wed, 11 Jan 2017, Maciej W. Rozycki wrote:
> > > In any case, the soft-fp change is relevant in the hard-float case as
> > > well, to make software TFmode behave consistently with hardware SFmode
> > > and DFmode regarding NaN payload preservation.
>
> Is mixing TFmode, DFmode and SFmode oper
Maciej Rozycki writes:
> On Thu, 5 Jan 2017, Matthew Fortune wrote:
> > It is true to say that users are discouraged from using 2008-NaN with
> > soft-float for pre-R6 architectures simply to avoid further fragmentation
> > of software for no real gain. However, for R6 then soft-float is 2008-NaN
On Thu, 5 Jan 2017, Matthew Fortune wrote:
> > > AFAIR we deliberately decided not to define a 2008-NaN soft-float
> > > ABI, and chose to require all soft-float binaries to use the legacy
> > encoding.
> >
> > Soft-float and 2008-NaN are naturally completely orthogonal and the
> > combination w
Joseph Myers writes:
> On Wed, 4 Jan 2017, Maciej W. Rozycki wrote:
>
> > AFAIR we deliberately decided not to define a 2008-NaN soft-float
> > ABI, and chose to require all soft-float binaries to use the legacy
> encoding.
>
> Soft-float and 2008-NaN are naturally completely orthogonal and the
On Wed, 4 Jan 2017, Maciej W. Rozycki wrote:
> AFAIR we deliberately decided not to define a 2008-NaN soft-float ABI,
> and chose to require all soft-float binaries to use the legacy encoding.
Soft-float and 2008-NaN are naturally completely orthogonal and the
combination works fine (of course
On Wed, 4 Jan 2017, Matthew Fortune wrote:
> > The MIPS sfp-machine.h has an _FP_CHOOSENAN implementation which
> > emulates hardware semantics of not preserving signaling NaN payloads for
> > an operation with two NaN arguments (although that doesn't suffice to
> > avoid sNaN payload preservation
Joseph Myers writes:
> The MIPS sfp-machine.h has an _FP_CHOOSENAN implementation which
> emulates hardware semantics of not preserving signaling NaN payloads for
> an operation with two NaN arguments (although that doesn't suffice to
> avoid sNaN payload preservation in any case with just one NaN
The MIPS sfp-machine.h has an _FP_CHOOSENAN implementation which
emulates hardware semantics of not preserving signaling NaN payloads
for an operation with two NaN arguments (although that doesn't suffice
to avoid sNaN payload preservation in any case with just one NaN
argument).
However, those ar