Re: [gentoo-embedded] gcc configure for ARM ep93xx: --with-float-abi= does not exist

[Jakub Ladman]

Because of reading this message, i am trying to create toolchain (with 
crossdev) for the maverick crunch again.
I made a try with gcc-4.3.2 and 4.1.2, but both failed with this messages:

collect2: ld terminated with signal 8 [Výjimka matematického koprocesoru 
(SIGFPE)] during the last stage - compiling C++ compiler.

I have czech localization, so:
Výjimka matematického koprocesoru = FPU exception

What you think about?

Jakub Ladman
 Dne Wednesday 03 of December 2008 12:44:34 Martin Guy napsal(a):
> Hi
>   I too have been trying to set hard maverick crunch FPU code
> generation as the default for a compiler here, and I see some people
> here made the same mistake of configuring GCC using
> --with-float-abi=softfp
> This option does nothing and is silently ignored (well ok, "configure"
> sets $with_float_abi but nothing ever inspects that) - you still have
> to supply --with-float-abi=softfp at runtime to get hard FP
> instructions, obtaining soft float otherwise.
>
> There is currently no way to select softfp Maverick code generation by
> default. for GCC 4.3.2, the closest configure options are, as well as
> --with-float=softfp and --with-fpu=maverick:
>
> --with-arch=armv4t the build fails when it tries to compile hard FPA
> instructions into libgcc,
> --with-cpu=ep9312 it compiles armv5t instructions into libgcc
> --with-arch=ep9312 the assembler barfs saying that ep9312 is not a
> recognised architecture.
>
> There is even one check that looks for --target=ep9312-* and selects
> default fpu=Maverick but I very much doubt that works.
>
> This whole area is bit-rotten. I think the 'ep9312' should be
> eliminated,or mapped into arm920t+maverick early on, and everything
> should work off -m[cf]pu= the same as every other fpu. Unfortunately,
> checks for ep9312 are spread through the config scripts and source
> like a fungus.
>
>     M