14:40:10drmeisterBike: Could there be too much inlining going on? Ironclad takes 5 hours to build.
14:41:10Bikei don't know how to gauge. but i doubt there could be "too much" except for recursive failures or something. we hardly inline anything, really
14:41:22drmeisterOr poor choices and results in a fasl that is 218MB
14:53:48beachCan you tell whether it is the compiler itself, or Clasp that makes it that slow?
14:53:56drmeisterIronclad is a special case - with babel as a close second - I haven't seen any other library take so much time and generate so much code.
14:54:46Bikebeach: cleavir runs orders of magnitude more quickly on sbcl
14:54:47drmeisterI can't tell if it's the compiler, or Clasp.
14:55:25drmeisterRight - that's where we get back to optimization.
14:55:44drmeisterI'll be curious to see how much faster cleavir on sbcl compiles cclasp.
14:56:32Bikethere are things in cleavir that can and should be sped up, but i think the main losses in clasp are rather due to bad fundaments
14:56:51Bikefor example, we spend a lot of time on make-instance - like 40% was it? - which ctors can help with