
On Tue, Oct 10, 2006 at 01:31:58PM +0200, Matthias Fischmann wrote:
What qualifies as constant applicable form, and why is it not labelled in a more informative way?
CAFs are, AIUI, things that are just values (i.e. things that don't take an argument) that have been floated up to the top level. Compiling with -caf-all might give you more useful information. If that doesn't help then you might find it helpful to look at heap profiles rather than just the normal profiler output.
Why are there functions that inherit all of their (considerable) time and space consumption from elsewhere, but nothing in the list would allow for such a rich inheritage?
I didn't understand that. If it's possible to give a small example then that might help? Thanks Ian