Paolo Bonzini writes:
> On 08/03/2011 03:46 PM, Rainer Orth wrote:
>>
>> Ok for mainline if they pass?
>
> I think the avr-lib.h and h8300-lib.h files should be modified to only
> define the constants when compiling fp-bit, because they pollute the
> namespace.
>
> Both avr and h8300 only use flo
On 08/03/2011 03:46 PM, Rainer Orth wrote:
Ok for mainline if they pass?
I think the avr-lib.h and h8300-lib.h files should be modified to only
define the constants when compiling fp-bit, because they pollute the
namespace.
Both avr and h8300 only use floats, so you can wrap them in #ifdef
Joseph S. Myers wrote:
> The SPU format doesn't support NaNs, so the value of this field isn't
> particularly meaningful for SPU. I'm not clear why SPU is actually using
> fp-bit; what functions from fp-bit will actually end up getting used by
> code built for SPU, and how close does fp-bit ge
On Wed, 3 Aug 2011, Rainer Orth wrote:
> * Even worse, there are a couple of formats/targets that do use
> fp-bit.c, don't yet define QUIET_NAN_NEGATED, but have qnan_msb_set =
> false:
>
> qnan_msb_setuses fp-bit
>
> mips_single_forma
On Fri, 22 Jul 2011, Rainer Orth wrote:
> * Provide fpbit_wrap_start/fpbit_wrap_end as in soft-fp, which is a
> general solution.
>
> * Use configure tests. My current preference would be to use
> AC_CHECK_SIZEOF([double]) (for rx) and AC_CHECK_SIZEOF([long double])
> (for mips) and substi
Joseph,
>> -tp-bit.c: $(srcdir)/config/fp-bit.c
>> -echo '#ifdef __MIPSEL__' > tp-bit.c
>> -echo '# define FLOAT_BIT_ORDER_MISMATCH' >> tp-bit.c
>> -echo '#endif' >> tp-bit.c
>> -echo '#if __LDBL_MANT_DIG__ == 113' >> tp-bit.c
>> -echo '#define QUIET_NAN_NEGATED' >> tp-bit.c
>>
On Tue, 12 Jul 2011, Rainer Orth wrote:
> Only a couple of special defines (like FLOAT_WORD_ORDER_MISMATCH,
> QUIET_NAN_NEGATED) are moved to special t-* files in libgcc/config with
> [FDT]PBIT_CFLAGS similar to e.g. LIBGCC_SYNC_CFLAGS. If it were
> possible to have gcc define some __LIBGCC_* mac
On 07/12/2011 10:07 AM, Rainer Orth wrote:
> Only a couple of special defines (like FLOAT_WORD_ORDER_MISMATCH,
> QUIET_NAN_NEGATED) are moved to special t-* files in libgcc/config with
> [FDT]PBIT_CFLAGS similar to e.g. LIBGCC_SYNC_CFLAGS. If it were
> possible to have gcc define some __LIBGCC_* m
