Duncan Coutts wrote:
On Wed, 2005-02-02 at 13:30 -0700, Seth Kurtzberg wrote:
Duncan Coutts wrote:
In these cases we cannot turn on traditional profiling since that would
interfere with the optimisations we are relying on to eliminate most of
the other memory allocations.
I don't understand why you can't use profiling as a debugging tool. How
would profileing, ifor test purposes, cause other things to break?
The problem is that profiling add in extra parameters and extra code to
each function (each SCC). This can interfere with optimisations like
inlining and unboxing I believe. Simon could explain it better.
Generally profiling is great, but for some of these low level
optimisation problems you can end up profiling a different program
program to the one you are interested in (the unoptimised one rather
than the optimised one).
Yes, I can see that. I've had problems in other languages where using
the debugger stopped a seg fault. Obviously not the same situation, but
a similar problem. Have you come up with a solution?
Duncan
!DSPAM:420176b7116488359410460!
_______________________________________________
Glasgow-haskell-users mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
