> I just had this crazy idea of new tooling that would help the curious > programmer to find the line of code that triggers a lot of allocation, > or find the line of code that causes a lot of GCs.
One could extend the profiling machinery to also trace and count allocations (the compiler already keeps track of the amount of memory allocated inline in each CPS procedure, this would have to also take non-inline allocation into account). The problem is that CPS heavily transforms the source code, but it would be a start. felix _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
