Am Mon, 17 Feb 2014 10:00:48 +0200 schrieb Riku Voipio <riku.voipio@iki.fi>: > Thanks Peter for explaining, this was how I ended up the suggestion > in the bug. > > > I see. In that case, I'll have to leave the package as it until > > something along those lines is implemented. > > Yes. The ideal solution is for the upstream to implement cpu runtime > detection that: > > 1) uses neon if it is available > 2) falls back to fixed point if app requested 16-bit playback > 3) finally falls back to generic fpu code if neither of above applies > > Any packaging level workaround is going to be suboptimal for someone. Isn't the approach for the linker to select libraries like libavcodec on the table anymore? I see that I'll have to add that float conversion code to keep the features along all builds, but selecting a vfp and non-vfp variant for fixed point or floating point via the linker seems like the most clean approach you are going to get. NEON detection may come... but if we have linker selection, that would be covered right now. So ... can I get away with adding that stupid float conversion, so folks have reasonable performance in likely applications of debian on ARM, please? ;-) Alrighty then, Thomas PS: I'll have to remove those "experimental" markings from the nofpu variants in configure help. They are getting old.
Attachment:
signature.asc
Description: PGP signature