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
On 02 February 2005 18:42, Duncan Coutts wrote:
On Wed, 2005-02-02 at 17:01 +, Simon Marlow wrote:
On 02 February 2005 13:38, Duncan Coutts wrote:
Would looking at the core files help? What would I be looking for?
Here's a simple version that I would expect to run in constance
space.
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
On Wed, 2005-02-02 at 17:01 +, Simon Marlow wrote:
On 02 February 2005 13:38, Duncan Coutts wrote:
Would looking at the core files help? What would I be looking for?
Here's a simple version that I would expect to run in constance space.
pixbufSetGreen :: Pixbuf - IO ()
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
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
