Subject:
|
Re: Copy of MacMegaPov 0.7
|
Newsgroups:
|
lugnet.cad.dev.mac
|
Date:
|
Tue, 31 Jul 2007 04:29:17 GMT
|
Viewed:
|
7872 times
|
| |
| |
In lugnet.cad.dev.mac, Travis Cobbs wrote:
|
In lugnet.cad.dev.mac, Allen Smith wrote:
|
The version I posted does not require Classic. Its an old CFM Carbon
program (not Mach-O) that can run natively under both OS 8/9 and OS X. It is
PowerPC though, so on an Intel Mac, it gets emulated via Rosetta. (But I
suspect it runs faster there than it does on my Powerbook G4!)
|
Sorry. I used the command line unzip (on my Macbook) to unzip the file, and
that toasted the contents. Apparently the resource fork didnt extract
properly. Using a different unzipper solved the problem.
|
For comparison, I rendered m6459.png (picture posted in earlier post) at
640x480, and the times were as follows (all on an original MacBook 2GHz).
Intel (command line-only) compile:
Time For Trace: 0 hours 0 minutes 2.0 seconds (2 seconds)
Time For Post: 0 hours 0 minutes 1.0 seconds (1 seconds)
Total Time: 0 hours 0 minutes 3.0 seconds (3 seconds)
|
|
Your PPC (Carbon with UI) compile:
Time For Trace: 0 hours 0 minutes 8.0 seconds (8 seconds)
Time For Post: 0 hours 0 minutes 5.0 seconds (5 seconds)
Total Time: 0 hours 0 minutes 13.0 seconds (13 seconds)
|
|
My PPC (command line-only) compile (different compiler, and no UI):
Time For Trace: 0 hours 0 minutes 8.0 seconds (8 seconds)
Time For Post: 0 hours 0 minutes 2.0 seconds (2 seconds)
Total Time: 0 hours 0 minutes 10.0 seconds (10 seconds)
|
|
Not sure why all the times are rounded (truncated?) to the nearest second, but
there is a noticeable difference between all three versions. Your compile has
the huge advantage of an actual UI, though. Its very odd that only the
post-processing step took longer on yours, and not the trace. My guess is that
there is something in there that the current GCC optimizes better than whatever
compiler compiled yours (at least when running under Rosetta).
--Travis
|
|
Message is in Reply To:
| | Re: Copy of MacMegaPov 0.7
|
| (...) Sorry. I used the command line unzip (on my Macbook) to unzip the file, and that toasted the contents. Apparently the resource fork didn't extract properly. Using a different unzipper solved the problem. --Travis (17 years ago, 31-Jul-07, to lugnet.cad.dev.mac, FTX)
|
18 Messages in This Thread:
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|