I compiled modfied  UNIX sources  with hardware square root  __fsqrt()
substituted for sqrt() in XCODE version 1.1  .
I got about 32 minutes render time on a dual 2Ghz G5 Mac for benchmark.pov
using the benchmark.ini settings file

My conclusion is that you burn up all of the G5 optmizations in GCC3.3 just
to catch up about even with a CODE WARRIOR compilation.

I hard coded __fsqrt because a test on my machine shows erratic (or
non-existent) forced conversion  using the "Additional Compiler Flags" in
XCODE

A test on my machine shows that __fsqrt function executes about 6.8 times
faster than sqrt().

Post a reply to this message