In article <361### [at] khrimorjp> , "Y.Tanabe" <tec### [at] khrimorjp> wrote:

>I upload Pov-Ray3.1 and pov-ray3.1e for (G3)Power PC603.
>
>Pov-Ray3.1 is compiled by MPW MrC(3.5d3) optimizer is local
>skyvase.pov 640 x 480 -------------------- 3 minutes 50 seconds
>
>pov-ray3.1e is compiled by MPW MrC(3.5d3) and Mac Part is same as
>POV-3.02 TE32K
>skyvase.pov 640 x 480 -------------------- 2 minutes 45 seconds
>
>the above bench with Power PCG3(233 MHz) Ram 96 MByte with VM is on

Yes, this is why we would have liked to use MrC for the official version (and why I
created the MrC makefile), but StdCLib (any version of it!) or MrC itself create some
strange and very hard to track bugs which may cause POV-Ray to crash on complex scenes
(not because these are complex, but because of some memory copying problems, I
suspect). As a matter of fact, the reason why this MrC compile is slower than the last
one is because I carefully tuned *down* the optimizations to eliminate some other
errors. Have you tried blobs with your versions? We had problems with them as well as
long as optimization for this part of the code was on...

Well, for most scenes the MrC version is still useful. However, I would strongly
recomment to run *no* other applications with it. If it goes mad it will most likely
damage the systems heap structures and as the Mac has no memory protection (yet),
other applications may suffer. I had to reinstall my system several times during
development...

Just a warning, and the reason why we choose to the CW build.
Note that some of the problems definetly come from the StdCLib because our CW compile
with StdClib (instead of the MSL CLib) had some problems as well.


Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: Tho### [at] csicom

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://www.povray.org

Post a reply to this message