Thanks for your answer Benny.
I use the same tools version.
I can build successfully, but the problem is that when you just configure with
--without-fp, the build process still generates floating point instructions in some of
the library functions.
For example, if you run the arm-linux-objdump -d command on all libraries (using for i
in *.a; do; =) and then perform a grep -c stf *.out. This shows that libc.a and libm.a
(and the ..._p.a variants also) contain some Store Float instructions.
Amongst those functions are
__copysign
__modf
__scalbn
__frexp
__ldexp
__scalbnf
__frexpf
__ldexpf
__erand48_r
__strtof_internal
__strtod_internal
__strtof_l_internal
__strtod_l_internal
__strfmon
__strfmon_l
_IO_vfprintf
__printf_fp
printf_size
_IO_vfscanf
...
and much more.
I wanted to pass explicitly -msoft-float to gcc as an argument, to ensure that no fp
instruction is used in the code generation.
But giving CFLAGS+=-msoft-float as argument to make doesn't work.
I finally edited the Makeconfig file to change the default arguments given to gcc
(adding -msoft-float).
Then I finally managed to build the glibc (this noon) ....
Even if the process dramatically reduced the number of floating points instructions,
there are still a few ones...where they should not be.
I am investigating the way they are generated, and I am afraid I will have to ask for
some help !
Cyril Germond
Competence Center Platforms
PHILIPS Semiconductors Sophia
505, route des Lucioles
Sophia Antipolis - 06560 Valbonne - France
Tel +33 (0)4 92 96 83 63
Fax +33 (0)4 92 96 12 66
E-mail : [EMAIL PROTECTED]
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
