🚀 go-pugleaf

Ah, but HOW would you "regularly interrupt program execution"?

In article <8ggcq7$jmp$1@hyperion.triode.net.au>,
  <telford@xenon.triode.net.au> wrote:
> In alt.mud.programming CoolFish <coolfish@bigpond.com> wrote:
[snipped]
> > with an Intel Pentium (x86) processor running the WIndows 2000 or
Win NT
> > operatinf system.
> > The driver has to provide for initialising, starting, stopping and
reading
> > the timer.  The timer will be
> > used for timing the executions of a small segment of code within a
program.
>
> I hope I'm not too rude in saying that this is a really shithouse way
to
> time code execution. If you want your code to run fast and need to
identify
> where the time is spent then regularly interrupt the execution and
look
> at the program counter value (read how profiling works with
linux/gcc/gprof).
> After time you see which regions the program counter is most often in.
>


Sent via Deja.com http://www.deja.com/
Before you buy.