On Tue, 13 Aug 2013, Richard Sandiford wrote:
> > I've had a look now and that is related to the width of `long' on the
> > host -- encode_ieee_double returns its output 32-bit bit patterns in a
> > buffer of signed longs. The arithmetic value of these patterns therefore
> > depends on whethe
"Maciej W. Rozycki" writes:
> I've had a look now and that is related to the width of `long' on the
> host -- encode_ieee_double returns its output 32-bit bit patterns in a
> buffer of signed longs. The arithmetic value of these patterns therefore
> depends on whether the width of `long' is 3
On Tue, 2013-08-13 at 14:28 +0100, Maciej W. Rozycki wrote:
> This has passed mips-linux-gnu regression testing on a 32-bit host, but I
> can't regression-test a 64-bit host easily -- Steve, can you please verify
> that this change indeed works for you? Richard, OK to apply assuming that
> it
On Wed, 7 Aug 2013, Richard Sandiford wrote:
> > When I run two of your new tests in gcc.target/mips (nan-legacy.c and
> > nans-legacy.c), they are failing because my GCC is putting out
> >
> > .word 4294967295
> >
> > instead of
> >
> > .word -1
> >
> > like the test is expecting.
>
"Steve Ellcey " writes:
> Maciej,
>
> When I run two of your new tests in gcc.target/mips (nan-legacy.c and
> nans-legacy.c), they are failing because my GCC is putting out
>
> .word 4294967295
>
> instead of
>
> .word -1
>
> like the test is expecting.
>
> I believe they are equi
Maciej,
When I run two of your new tests in gcc.target/mips (nan-legacy.c and
nans-legacy.c), they are failing because my GCC is putting out
.word 4294967295
instead of
.word -1
like the test is expecting.
I believe they are equivalent (0x) but I am not sure what
