Hi! taylanbayi...@gmail.com (Taylan Ulrich "Bayırlı/Kammer") skribis:
> Andy Wingo <wi...@igalia.com> writes: > >> On Wed 21 Sep 2016 23:01, taylanbayi...@gmail.com (Taylan Ulrich >> "Bayırlı/Kammer") writes: >> >>> By the way, compile time seems to increase greatly with 2.2, to the >>> point I wondered if it's really compiling in parallel, but it does seem >>> to as evidenced by top(1). Maybe package modules could be compiled with >>> certain optims turned off, since they mostly just consist of package >>> object definitions and not procedures whose performance would matter. >> >> How much? > > Running make, then make clean-go, then 'time make', we get: > > Guile 2.0: > real 2m46.405s > user 6m39.044s > sys 0m2.140s > > Guile 2.2: > real 31m44.433s > user 84m32.060s > sys 0m10.880s [...] > Using optim level 1, compilation takes the same amount of time *and* I > get a segfault at the end. When re-running make, it finishes by > compiling only gnu/packages/python.go (indicating that all other .go > files were compiled successfully on the first run), and this time > succeeds without a segfault. > > Using optim level 0, it seems to hang at gnu/packages/shells.go. (More > precisely, I aborted after a total of 118 minutes, most of which was > spent waiting for shells.go to finish.) This sounds a bit concerning. Any idea what’s going on? I think we should make sure we have a way to build with 2.2 in at most the same amount of time as with 2.0. (Easier said than done! ;-)) Ludo’.
