Hello Zdenek,
Tuesday, August 28, 2001, 1:32:11 PM, you wrote:
ZK> Hi all
ZK> I've started to build library which should collect routines which
ZK> might be accelerated by using MMX, SSE, 3DNow and other CPU extension.
ZK> As I'm using just MMX procesor do not expect I'll be programing
ZK> something for PIV or Athlon.
ZK> Anyway - currenly its just first approximation of the interface -
ZK> if anyone has idea what could be made better - this is right time
ZK> for doing so.
ZK> Here are some basic principles:
ZK> 1.) Library should be renentrant (so it shouldn't be problem to use it
ZK> threaded application)
ZK> 2.) Should have very limited amount of call
ZK> - so it would be easily usable with: dlopen, dlsym
ZK> 3.) Should be able to pick the best routine at runtime according to the
ZK> current CPU - but should containt all routines for given platform
ZK> - e.g. when I make debian package user of PIII will use same library and
ZK> will use PIII code and P5 user will use nonaccelerated plain C version
ZK> of the code while Athlon user could use 3DNow version if such routine
ZK> exists.
ZK> 4.) usage should be SIMPLE.
ZK> 5.) should be able to work on more platforms - e.g. alpha users could
ZK> write their own routines.
ZK> Sun users shuold be able to easily map calls to their mediaLibs
ZK> expecting comments....
What routines are you going to optimize? Only those that are used by
libaviplay? Or including avirecompress and ffmpeg? Or something more
global? Let's start with defining a scope of the library ...
--
Best regards,
Eugene
mailto:[EMAIL PROTECTED] or [EMAIL PROTECTED]
[Team GADGET] [Team Two Divided By Zero]
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
