From:	leathm AT solwarra DOT gbrmpa DOT gov DOT au (Leath Muller)
Message-Id:	<199710100106.LAA20582@solwarra.gbrmpa.gov.au>
Subject:	Re: Profiling allegro apps
To:	eldredge AT ap DOT net (Nate Eldredge)
Date:	Fri, 10 Oct 1997 11:06:23 +1000 (EST)
Cc:	1Stein AT gmx DOT de, djgpp AT delorie DOT com
In-Reply-To:	<199710100003.RAA14883@adit.ap.net> from "Nate Eldredge" at Oct 9, 97 05:03:36 pm

> >does anybody know how to profile code written with djgpp and allegro. gprof
> >doesn't work because no profiling data is produced by the executable. I've
> >tested it with a simple Hello-world program and it worked. Could it be that
> >the timer code of allegro kills the profiler code inside the executable?

> Yeah, I think that's the case. Shawn?
> You might be able to implement some limited profiling by using an Allegro
> timer as a counter, and printing its value at various strategic places in
> the code.

If your on a Pentium - use its internal counters... :) That way you don't
have to worry about profiling stuff with gcc - you can use CPU specific
timing...

Leathal.

- Raw text -