On Sat, Aug 30, 2003, Alexander R. Pruss wrote:
Are there any good profiling solutions for optimizing code (68k at
least)?
Don't forget to use the --enable-debug-labels option when you build
the viewer to get the function names included in POSE's profiling
output.
/Mike
On Sat, 30 Aug 2003 7:31am, Alexander R. Pruss wrote:
This is not Plucker-specific, but I thought someone would know. Are
there
any good profiling solutions for optimizing code (68k at least)? And
is
there a version of POSE that has exact instruction timings (so that
speed on
that version
This is not Plucker-specific, but I thought someone would know. Are there
any good profiling solutions for optimizing code (68k at least)? And is
there a version of POSE that has exact instruction timings (so that speed on
that version is the same as speed on an actual 68k device)?
Alex
--
Dr
