freenode/#clasp - IRC Chatlog
Search
11:23:17
stassats
just reducing compilation size is just plugging holes, i'd rather make it involve zero compilation for constants
13:51:34
drmeister
I know - just sayin. Well, IIRC it was down to about 28min before Bike switched to SSA for temporary variables.
13:51:54
stassats
i would've tried less compily constants on my own, but 40 minute build times and c++ discourage me
13:52:53
drmeister
Bike: Not you - the SSA for temporary variables might have shifted the burden elsewhere within llvm.
13:54:00
drmeister
Could you confirm my suspicions tomorrow? Pick the commits before the temporaries and after the temporaries and then build those.
13:55:27
drmeister
I'd like to measure the build time, the code size and the number of landingpads due to the changes in how temporaries are handled and stackmaps.
13:57:47
drmeister
I can't be sure if the build time is slower because I could have done something that slowed it down. I've had build times jump around by factors of 2x to 8x due to power management and build configurations.
13:59:27
drmeister
We also need to measure how fast the cleavir compiler is within cclasp. bclasp+cleavir building cclasp is one thing, but cclasp compiling say a quicklisp system is something else and improving that performance is more important than build time.
14:00:18
drmeister
I've just noticed over the last couple of days that the build time was down to about 28min then it jumped up to 1hr and now it's down to 49min.
14:12:32
drmeister
I just can't be sure about my build time observations because they stretch over weeks and my machine isn't carefully set into a calm state before building.
14:17:40
drmeister
We've made a lot of changes over the last weeks and they have (1) cut the size of the generated code from about 25M lines to about 8.6M lines, (2) convert cleavir SSA variables to llvm SSA variables, (3) made the build more parallel.
14:22:55
drmeister
Then there is this - we have a buildbot that has been building docker images - it has an overall build time of about 2.5hrs
14:23:41
drmeister
Those are builds over the last week or so - they have changed very little. I can dig into those and pull out more build time data. That is better than times from my laptop.
14:25:01
drmeister
But when building it on a 6 core machine using 12 processes and hyperthreading it takes about 23 min.
14:51:58
drmeister
I think I was misremembering the 28min builds - maybe that was just for cclasp. It takes 20 min just to get through the C++ compilation, aclasp and bclasp.
15:29:07
drmeister
Yeah - the single executable cclasp-boehm has trouble with stackmaps - checking...
15:31:26
drmeister
It appears that there is a problem with linking the stackmaps when I link everything together (sigh).
21:50:06
kpoeck
I think I have now a situation where a gethash on _lisp->_Roots._ClassTable returns nil
21:53:24
drmeister
Ok, there is supposed to be machinery to deal with that - but that is a very, very helpful observation.
21:55:23
kpoeck
Actually now when a symbol that should represent a class is not found, I do a second test with maphash and if I find the symbol I return the class.