RE: RE: RE: Re: [MIPS r5900] libgcc floating point fixes

2014-08-18 Thread Jürgen Urban
> > When I compile for mipsel ABI o32 with -mhard-float and -msingle-fpu, It get > > the warning: > > > > Warning: float register should be even, was 1. > > > > I would say the warning is wrong, because odd FPU registers are available. > > This is wrong but this is the area which is in flux at t

RE: RE: RE: Re: [MIPS r5900] libgcc floating point fixes

2014-08-18 Thread Matthew Fortune
> > > > What is harder to fix about n32 than o32? > > > > > > "-msingle-float" with n32 creates 64 bit FPU instructions like dmtc1 and > > > dmfc1. So I can't compile it for r5900. When I disable it, I get > internal > > > compiler errors. > > > > That certainly seems like a bug. Can you file a bug

Aw: RE: RE: Re: [MIPS r5900] libgcc floating point fixes

2014-08-03 Thread Jürgen Urban
Hello, > > > > Fixes for high level libraries should also be > > > > high level (dmult vs __FLT_MAX_EXP__); i.e. there should be no change in > > a > > > > different package which is specific for MIPS. The type double should > > stay > > > > double and is handled without a problem when the FPU is

RE: RE: Re: [MIPS r5900] libgcc floating point fixes

2014-07-28 Thread Matthew Fortune
> > > Fixes for high level libraries should also be > > > high level (dmult vs __FLT_MAX_EXP__); i.e. there should be no change in > a > > > different package which is specific for MIPS. The type double should > stay > > > double and is handled without a problem when the FPU is 32 bit in ABI > o32.