Re: help with mplayer bug 431139

[Tom Evans <tom@23palmer.net>]

Alternatively the code could have checks for the appropriate features by 
using the amask instruction and chose the correct code sequences - 
probably a win in the MVI cases, unclear about the itoft cases.

It would have to be looked at to see what code path tricks could be played.

Is this code in mplayer or libmpeg2?  (or is libmpeg2 included in mplayer!?)

...tom

A Mennucc wrote:
> This means that mplayer is compiled with 'gcc -mcpu=ev67 ' ;
> and also that  CAN_COMPILE_ALPHA_MVI is set, and this enables some
> specific code in  libmpeg2/  (I don't know what MVI is , alas - but it
> looks as something that not all CPUs have)
>
> So the simplest workaround seems to set -mcpu to some lower CPU and to
> disable MVI...
>
> a.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFG0dCb9B/tjjP8QKQRAnVNAJ9/rHMi2j49z1Uow3ZiCCT9prHTEACfQRso
> GpZPah4Qx7lpzUKnj34GUe0=
> =8jJN
> -----END PGP SIGNATURE-----
>
>
>