Re: [transcode-users] Wrong CPU flags detection

[achurch@xxxxxxxxxxx (Andrew Church)]

>On Mon, 2005-09-26 at 14:45 +0000, Andrew Church wrote:
>>      "3dnow" turning into "3dnowext" is another bug (fixed in CVS), but
>> there's no optimization using 3dnow instructions--your choices are C, pla=
>in
>> assembly, MMX, or SSE.  Since 3dnow isn't supported, transcode falls back
>> to C (i.e. libc memcpy).
>
>This seems to wrong to me, it should fall back to mmx.

     No, because 3dnow was user-specified; if you look at the code, it sets
_only_ that accel flag, as opposed to auto-detection which works like you
expect.  It would probably be more useful if you could give --accel
multiple flags to set (which is actually what I was planning to do along
with turning it into a developer-use hidden option if nobody complained).

  --Andrew Church
    achurch@xxxxxxxxxxx
    http://achurch.org/