Duncan Coutts wrote:

All,

I'm looking for advice on how to figure out why some piece of code is
allocating memory when I think it ought to be able to work in constant
space.

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?
<snip>


Duncan

_______________________________________________
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

!DSPAM:4200ddb972401401013949!




_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

Reply via email to