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
>
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
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 report for that with
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 the moment.
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 32 bit in ABI
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.
The
Jürgen Urban juergenur...@gmx.dewrites:
Jürgen Urban juergenur...@gmx.de writes:
Hello Richard,
Jürgen Urban juergenur...@gmx.de 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
Jürgen Urban juergenur...@gmx.dewrites:
Jürgen Urban juergenur...@gmx.de writes:
Hello Richard,
Jürgen Urban juergenur...@gmx.de 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
Jürgen Urban juergenur...@gmx.de writes:
Hello Richard,
Jürgen Urban juergenur...@gmx.de 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
Hello Richard,
Jürgen Urban juergenur...@gmx.de 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
Jürgen Urban juergenur...@gmx.de writes:
Hello Richard,
Jürgen Urban juergenur...@gmx.de 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
Jürgen Urban juergenur...@gmx.de 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
juergenur...@gmx.de
An: gcc-patches@gcc.gnu.org
Cc: juergenur...@gmx.de
Betreff: [MIPS r5900] libgcc floating point fixes
Hello,
I found a problem in GCC on MIPS r5900: When printf() is used with type
float, the converter function __extendsfdf2() is called. Parameters to
printf
Hello,
I found a problem in GCC on MIPS r5900: When printf() is used with type float,
the converter function __extendsfdf2() is called. Parameters to printf() are
always passed as double and not float. The function __extendsfdf2() calls
itself to convert 32 bit float to 64 bit float. With
14 matches
Mail list logo