Thorsten Glaser writes:
> Ingo Jürgensmann dixit:
>
> > echo line to know which module is currently compiled) you might find the
> > module
> > in question that generates that FPU error and investigate further then.
>
> It’s not an error. Python (rightfully) runs some FPU instruction,
>
Michael Schmitz dixit:
>> Maybe we can have a GCC -m* flag that tells it to not emit those
>> instructions? (Maybe call library functions then or something.)
>
> -msoft-float?
No, one that tells it to only skip those instructions that are
not available in the FPU emulation.
> Might be easier to
Thorsten,
Maybe we can have a GCC -m* flag that tells it to not emit those
instructions? (Maybe call library functions then or something.)
-msoft-float?
You don't want that enabled for machines that do have a FPU, though.
Might be easier to add the odd FPU instruction to the emulator than
Ingo Jürgensmann dixit:
> echo line to know which module is currently compiled) you might find the
> module
> in question that generates that FPU error and investigate further then.
It’s not an error. Python (rightfully) runs some FPU instruction,
it just happens to be one the FPU emulator lacks
4 matches
Mail list logo
