Bug#738981: Fwd: Bug#738981: Switch to use generic_fpu for ARM
peter green
plugwash at p10link.net
Mon Feb 17 00:28:30 UTC 2014
Reinhard Tartler wrote:
> I mean line 55
>
I've just looked at ./configure --help and AIUI there are four possible
values of --with-cpu for arm systems
--with-cpu=generic_fpu Use generic processor code with floating
point arithmetic
--with-cpu=generic_nofpu Use generic processor code with fixed
point arithmetic (p.ex. ARM, experimental)
--with-cpu=generic_dither Use generic processor code with floating
point arithmetic and dithering for 1to1 16bit decoding.
--with-cpu=neon Use code optimized for ARM NEON SIMD engine
(Cortex-A series)
--with-cpu=arm_nofpu Use code optimized for ARM processors with fixed
point arithmetic (experimental)
We can't use the neon option because no arm port of debian gaurantees
that neon will be available. So I belive until the no-fpu options are
made compatible with audacious and/or some form of runtime detection is
implemeted (either using ld.so.hwcaps to load different versions of the
library) we need to keep using --with-generic-fpu on all our arm ports.
>to limit the effect of not using a FPU to just armel.
Assuming generic_fpu uses the standard floating point functionality in
the C compiler it WILL use the FPU on Debian armhf and raspbian (but not
on armel)
More information about the pkg-multimedia-maintainers
mailing list