Woon yung Liu wries
> Bump! Sorry, but could I please get an answer? I'm willing to update the
> patch without
> credit, if necessary.
Hi WY,
Apologies for exceptionally slow response.
The patch you referenced is mostly OK but I would like to get the MIPS16 check
changed to a configure time ch
Hi Woon Yung,
Woon yung Liu writes:
> Thank you for your feedback.
>
> New changes in this updated version:
>
> gcc/config/mips/mips.c:added a check against the use of both -mips16 and
> -march=r5900.
> libgcc/configure.ac:added a check for the support of -mips16 by the
> target.
> libgcc/confi
"Jürgen Urban" writes:
> The problem happens with the r5900 hard float configurations, e.g.:
> configure --target=mipsel-linux-gnu --with-float=hard --with-fpu=single
> --with-arch=r5900
> I created the attached patch which fixes this problem for r5900 and
> another problem explained later.
> The
Hello Richard,
> "Jürgen Urban" writes:
> > The problem happens with the r5900 hard float configurations, e.g.:
> > configure --target=mipsel-linux-gnu --with-float=hard --with-fpu=single
> > --with-arch=r5900
> > I created the attached patch which fixes this problem for r5900 and
> > another pro
"Jürgen Urban" writes:
> Hello Richard,
>
> > "Jürgen Urban" writes:
> > > The problem happens with the r5900 hard float configurations, e.g.:
> > > configure --target=mipsel-linux-gnu --with-float=hard --with-fpu=single
> > > --with-arch=r5900
> > > I created the attached patch which fixes this
> "Jürgen Urban" writes:
> > Hello Richard,
> >
> > > "Jürgen Urban" writes:
> > > > The problem happens with the r5900 hard float configurations, e.g.:
> > > > configure --target=mipsel-linux-gnu --with-float=hard --with-fpu=single
> > > > --with-arch=r5900
> > > > I created the attached patch
"Jürgen Urban" writes:
> > "Jürgen Urban" writes:
> > > Hello Richard,
> > >
> > > > "Jürgen Urban" writes:
> > Is this something you
> > have recently developed outside of the mainline kernel or does it already
> exist.
> > I'm not aware of such logic in the MIPS kernel yet.
>
> Yes, this is de
> "Jürgen Urban" writes:
> > > "Jürgen Urban" writes:
> > > > Hello Richard,
> > > >
> > > > > "Jürgen Urban" writes:
> > > Is this something you
> > > have recently developed outside of the mainline kernel or does it already
> > exist.
> > > I'm not aware of such logic in the MIPS kernel yet.
>
> > > 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.
> > > > 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
> > 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
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
12 matches
Mail list logo
