WARNING: This server is unstable and will be retired in the next days.
If you want to keep this forum available, please request immediately a migration
on the Nabble Support forum.
Forums that don't receive any migration request will be deleted forever.
It appears to me (anecdotally) that most of the build time is spent
compiling Scheme code, rather than C code.
One idea I had been toying with is whether Guile could compile faster
if it had another copy of Guile already around, so it could skip the
portion of compile-time where the interpreter is running the compiler.
This is how most compilers do it - you want another C compiler around
to compile GCC, etc. I was afraid that this would result in a
too-complicated build system, but maybe not. Does anyone have
experience with implementing something like this?
On Fri, May 4, 2012 at 7:30 PM, Ludovic Courtès <ludo@...> wrote:
> I was looking at the “history chart” at
> <http://hydra.nixos.org/build/2517280#tabs-history>, which shows graphs
> of the build time and installed Guile size vs. commits. Timings must be
> taken with a grain of salt, because of variability on the build machines.
> Still, a couple of worthwhile observations:
> • commit 1af6d2a (“Minimize size of embedded syntax objects in
> psyntax-pp.scm”) reduced the installed size from ~14.6 MiB to
> ~13.3 MiB;
> • CSE led to a build time increase from 28m at
> <http://hydra.nixos.org/build/2413477> to 43m