Hello Jonathan,
No, it is not. It seems a gcc problem.
It has to do, that even on a machine without floating point, the compiler
is supposed to support certain floating-point operations.
I think it is the calling convention - meaning the calling convention
needs to
be defined for floating point, and the processor needs to be able to
handle this.
Next, if the floating point is absent, the compiler will use built-ins
for the floating point operations.
Q. Is there anybody having experience with this ?. Its just my guess, it
would be nice to
have some extra opinions.
Best Regards,
Henri.
On 10/16/2020 07:13 PM, Jonathan Wakely wrote:
On Fri, 16 Oct 2020 at 15:22, Henri Cloetens wrote:
Hello all,
I am working on a custom port of GCC, and now I am trying to compile
newlib with it.
Today, I ran in an error message, because my custom port does not handle
double.
Now, yes, that is quite normal, as the processor does not support
floating point.
Q. How should I resolve this ?. Is there any way to tell newlib
configure there is no double,
and there should be no routines using it ?.
I think there is probably a way to do that, but you should ask on a
newlib mailing list. newlib is not part of GCC.
