Bug#738981: Fwd: Bug#738981: Switch to use generic_fpu for ARM

[peter green]

On Sun, Mar 02, 2014 at 09:06:44AM -0500, Reinhard Tartler wrote:

> That sounds like if the mpg123 package should use:
>  
> on armel: --with-cpu=arm_nofpu
> on armhf: --with-cpu=arm_fpu
>
>
> Does this make sense to everybody?
>   
Seems sane to me. armv7 devices without neon are relatively uncommon so 
while it's important that they are supported it's IMO not vitally 
important to squeeze out every last drop of performance from them.

I wonder what we should use on raspbian? I haven't tested on a Pi yet 
but it seems that on all tests i've seen so-far the generic fpu code is 
quite a bit slower than the arm nofpu code. Is there any quality 
difference from using a fpu vs nonfpu decoder? If so how much 
performance degredation do you beleive should be accepted in exchange 
for that quality improvement.

Lennart Sorensen wrote:
> I think so.  armhf's current debian rules automatically picked arm_fpu
> with the new version's configure script, so at least that one doesn't
> seem to need any explicit help.  armel might though.
>   
IMO it's often better to be explicit about this sort of thing. While 
upstreams defaults may align with debian armhf's requirements at the 
present time and on the present build hardware such defaults are subject 
to change either as a result of upstream changes in new versions or as a 
result of different build hardware.