[Mplayer-dev-eng] processsor speciffic code

[Dariusz Pietrzak]

Hello,
 i'm confering with debian at Tonelli.sns.it about uploading mplayer into
debian unstable.  Besides unifying configs ( we need to handle all those
funny things like fonts/codecs/general configs, and resolve win32 dlls
stuff ) we are thinking about single-binary problem.
ie: mplayer detects cpu and compiles cpu-speciffic code. from debian's
perspective we're only considering x86 and sparc archs, and only x86 for
now.
We would like to have single package of mplayer, but we don't want mplayer
to run slow just because we compiler it with mcpu=i386.
So, we are thinking about a ways around - there is debian proposed policy
that makes all binaries put their cpu-specific code into shared libraries
and include the right one during runtine. But as I understand there would
be noticable performance penalty.
Another solution we thought about is having few most common setups - for
pentium,pII,pIII,pIV,k6,k6-2,duron/athlon and i386 just in case, package
would provide binaries like mplayer.athlon, mplayer.i386, little script
or installation script would run correct one.
There was idea like this:
> replace all
>  ...#ifdef  HAVE_MMX
> by
>    if( have_mmx)
but it would be a lot of work, wouldn't be nice and I suspect there would
be large speed penalties due to branch-prediction missess. On cpus like
pIV that would really hurt.

Maybe someone have better idea how to handle this?

We also think that we would deliver only a couple of video outputs -
namely sdl, ggi, x11 and xv.
Or maybe also dga, fbdev, svga and aa, and make users with different needs
use current practice - download cvs and build mplayer themselves.

regards, Eyck



_______________________________________________
Mplayer-dev-eng mailing list
Mplayer-dev-eng at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mplayer-dev-eng