Each time texutil_tmp.h is included by texutil.c, eight new functions are generated, four for texsubimage2d and four for texsubimage3d. Those functions are listed in the arrays seen at lines 488 and 500 of texutil_tmp.h
um, apart from partial code duplications, is there any reason not to break these functions out into all the different types so each conversion type is done as fast as possible. Looking at it atm, (using my unrelated exprience in audio sample format convertion) these could be dramatically spead up by doing doing up functions that deal exclusively with a particular conversion.
That's what the code does now.
This would also make it much easier later on to add further conversion types and methods.
Maybe I don't understand what you're saying.
-Brian
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel