Oops!  I have never actually looked at the POV source, so that comment of
mine was an educated guess.  Thank you for pointing out the error.

Nevertheless, I think I'll start researching what would be required to hack
up an unofficial 3DNow! aware version of POV.  At the very least it'll be a
learning experience...


Thorsten Froehlich wrote in message <35eef9b5.0@news.povray.org>...
>In article <35eede43.0@news.povray.org> , "Rik Ling" <rli### [at] pipcomcom>
wrote:
>>  Certainly
>>your overall system performance will suffer but programs like POV, which
>>have a very tight execution loop that has been (hopefully) optimized to
stay
>>within the 16 to 32KB of on-chip cache, won't care about that.
>
>Basically ray tracers could be this way (if you only use planes and
spheres), but there is *no* way to get the ray tracer code POV-Ray has into
such a small cache!  And don't forget the data (our scene) - so ray tracing
*is* one of the few programs where you will (or should) notice a fast memory
interface (and 2nd level cache).
>
>
>Thorsten
>
>____________________________________________________
>Thorsten Froehlich, Duisburg, Germany

Post a reply to this message