[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

On Sun, Mar 02, 2014 at 12:02:40PM +0100, Thomas Orgis wrote:
> After Tahei didn't stop at this (big thanks from here!), we got a new
> snapshot,
> 	http://mpg123.org/snapshot/mpg123-20140302115523.tar.bz2 ,
> that will hopefully become mpg123 1.19.0 soon (not 1.18.x
> because of feature additions regarding this very debian issue). The
> main points:
> - float output with all decoders (also arm_nofpu)
> - ARM decoders (esp. NEON) working with debian toolchain
> - new --with-cpu=arm_fpu choice with runtime detection to switch
>   between NEON or normal FPU
> So, the number of builds for optimal treatment of differing platforms
> reduces to two:
> 1. --with-cpu=arm_nofpu
> 2. --with-cpu=arm_fpu
> I hope we can all be happy about that. I'd also be glad to get some
> confirmation from debian that it really works now. Release will be
> imminent, then.
> Thanks for staying with us with all the chattering about this ...

I now see (with arm_fpu of course, which it seems to have auto detected correctly):

perl scripts/benchmark-cpu.pl `which mpg123` /convergence_-_points_of_view/*mp3
Found 3 CPU optimizations to test...

#mpg123 benchmark (user CPU time in seconds for decoding)
#decoder        t_s16/s t_f32/s
NEON    7.58    7.84
generic 19.23   14.56
generic_dither  20.97   14.54

Looks good.  I ran it 3 times and they were very close, and the cpu pinned
itself at 1.5GHz during the test, and went back to 1.0GHz when idle again.
One of the two cores was very bored though with nothing to do.

Len Sorensen

Reply to: