From: Jeff E. <je...@in...> - 2001-03-09 03:56:54
|
[I sent this earlier, but as far as I can tell it bounced rather than being delivered] On Thu, Mar 08, 2001 at 10:39:11AM -0700, Keith Whitwell wrote: > You may want to avoid sharing the nv-specific stuff, but any progress on otf > codegen has lots of application beyond that extension -- I can think of a > dozen uses for something like this. Like Josh Vanderhoof's code, my code writes a file which is intended to be fed to the compiler. This is good enough for a proof-of-concept, but not good enough for the real world, as observed in a later post by Steve Baker, at least without some way to explicitly ask for the code you need before you start doing the actual rendering. A real, no-compiler, no-assembler target for texturing on MMX would be a fun week-or-two project[*], but portability would be very nearly zero, and it's not clear how much people care about software texturing these days anyhow. A project might use the GNU Lightning "portable assembler" JIT, but it would probably not be much faster than the current code since it makes such minimal assumptions about machine architecture (6 32-bit integer registers, for instance) so it can be portable, rather than generate blindingly-fast code. Jeff * And another year making it "right" in all the corner cases |