debugging memory allocations
simonmar at microsoft.com
Thu Feb 3 04:58:59 EST 2005
On 03 February 2005 00:41, 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
> 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.
Yes. Those pesky SCC annotations get in the way of optimisations. It's
possible (likely even) that we could do a better job here, profiling is
long overdue for an overhaul.
More information about the Glasgow-haskell-users