4) Can't do it. i386 != MMX. MMX is defined when the processor is anyAah. OK, that makes (a bit more) sense now. Maybe having MMX and MMX64 would be clearer?Maybe keeping MMX but changing i386 to MMX32 would be clearer. My only reservation is that much of this code is borrowed and this might complicate syncing with the original code.
If the original code has no 64bit specific asm, then we need to do something slightly incompatible anyway.
Maybe keep MMX as is (conceptually meaning USE_MMX), and add both MMX32 and MMX64 for incompatible blocks?
...
in avlib we are stuck with the existing defines (for syncing reasons),
Waiting for them to start adding 64bit code would be the lazy, and guaranteed compatible, way :-)
...
Nothing prevents you from using runtime detection in PowerPC world while we lag behind in x86 world.
I don't have the motivation to look into G5 acceleration. By the time someone else does, hopefully libavcodec will define MM_G5 or MM_ALTIVECG5.
-- Nigel Pearson, [EMAIL PROTECTED] | "Gentlemen, Telstra BI&D, Sydney, Australia | you can't fight in here Office: 8255 4222 Fax: 8255 3153 | - this is the war room!" Mobile: 0408 664435 Home: 9792 6998 | Dr Strangelove
_______________________________________________ mythtv-dev mailing list mythtv-dev@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
