[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] Re: #458: Chicken can't profile itself
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] Re: #458: Chicken can't profile itself |
Date: |
Thu, 03 Feb 2011 10:16:35 -0000 |
#458: Chicken can't profile itself
-----------------------+----------------------------------------------------
Reporter: sjamaan | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: 4.7.0
Component: compiler | Version: 4.6.x
Resolution: | Keywords: expander, profiler, self-compilation
-----------------------+----------------------------------------------------
Comment(by sjamaan):
It all started when Moritz was complaining that compiling (I think it was)
his new egg for pulseaudio took too long.
So I thought it would be a good idea to try building chicken for profiling
itself because I had no idea where it was spending most of its time. I
assume it's in the macro expansion (he uses two rather large macros), but
profiling just the expander itself is not enough; it will use procedures
from library and other core units, which should also be compiled with
profiling info so you can see what exactly is the reason for slowness.
More in general, I'd like to have an idea of where the compiler's
performance can be improved without a specific idea of what exactly I want
to profile.
Up till now I've been able to produce a working profiling chicken by
manually interfering with the compilation process and disabling profiling
for two units; the profiler itself and another which I can't remember
right now. Probably library.scm?
--
Ticket URL: <http://bugs.call-cc.org/ticket/458#comment:10>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.