This is the mail archive of the
mailing list for the GCC project.
Re: Soft floating point emulation problems
- To: cyril dot germond at philips dot com
- Subject: Re: Soft floating point emulation problems
- From: Richard Earnshaw <rearnsha at arm dot com>
- Date: Mon, 22 Oct 2001 16:20:22 +0100
- cc: linux at lists dot arm dot linux dot org dot uk, gcc at gcc dot gnu dot org, Richard dot Earnshaw at arm dot com
- Organization: ARM Ltd.
- Reply-To: Richard dot Earnshaw at arm dot com
> Even if the process dramatically reduced the number of floating points instructions, there are still a few ones...where they should not be (AFAIK)!!!
> For example, in the library libm.a, there are 3 stf instructions.
> 290: adad51ec stfges f5, [sp, #944]!
> 308: bd241146 stflts f1, [r4, -#280]!
> 470: bd241146 stflts f1, [r4, -#280]!
> I am quite confused !
> I am wondering if I should have had generated gcc itsel with some kind of -msoft-float option (it was generated with -nfp in the configuration script).
> Maybe is it a gcc configuration bug ?
> Has anyone information about this problem ?
> Does anyone know where could I find a set of floating-point instructions library ?
1) Are you sure these are really instructions in the code, and not
constants in constant pools? The latter is quite probable, and the
disassembler can't tell this (find the object file containing this
instructions, compile the file to assembly and look for the same
instructions in the output file).
2) If they are real FP instructions, are they coming from asm statements
in the source?