At 10:51 AM -0700 10/12/99, Afshan Jamil Raees wrote:
>Then what does the __profile__ macro does in CodeWarrior? I thought that
>would allow you to generate some profiling info...
That might be useful for Mac simulator builds, but it won't actually help
you profile on the 'real' hardware.
Using the emulator (Poser) is the best way to go. It give you cycle-count
accurate (more or less) timings of each function. Depending on Keith's
release cycle, it may even be able to give you instruction-level timings
for a given function. That is, you can find out how many times each 68K
instruction is executed for a given function, and how much of the overall
time was spent on that instruction. ...that'll tell you which loops need
optimizing.
The readme files that come with Poser should tell you everything you need
to know about how to profile your app. Odds are good you won't even have
to recompile it. :-)
--Bob
