freenode/#clasp - IRC Chatlog
Search
18:54:11
drmeister
I'm wondering how it was generated. It's slow to compile because it builds code to build hashtables.
19:03:10
kpoeck
with https://github.com/clasp-developers/clasp/blob/dev/src/lisp/kernel/lsp/encodings.lsp#L150
19:03:58
drmeister
It looks like Clasp doesn't compile long lists very well. That might be a file that we can rearrange to compiler better if we have the original generator.
19:08:49
drmeister
kpoeck: I mean you have a generator that generates a bunch of code that clasp then compiles.
19:12:00
drmeister
But I was thinking of running whatever code generates the load-time-value list of list of lists.
19:17:18
Bike
i'm not sure what to do about compiling lists any faster cos we're already technically doing it wrong
19:24:27
Bike
althrough wait, how is compiling literals even a problem now? don't we just generate a huge bytevector and a call to the literal VM thingie?
19:25:03
drmeister
I just noticed a long delay at the end of compiling cclasp and checked and it was taking a long time compiling generated-encodings.lsp .
19:26:12
drmeister
It's just that the generator generates the worst kind of large data generating source file that it could.
19:28:05
Bike
i'm not s ure how this function is used exactly, but basically it takes a constant list and builds a hash table out of it when called
19:28:20
Bike
actually, why is it even (load-time-value (list ...))? can we not just use a quoted list?
19:34:31
Bike
well what i mean is like, is this function going to be called more than once for the same encoding? the hash tables are effectively constant, i would imagine
19:53:40
kpoeck
(time (compile-file "/Users/karstenpoeck/lisp/compiler/clasp-karsten/src/lisp/kernel/lsp/generated-encodings.lsp")) -> 39.741 secs
20:15:15
Bike
kpoeck: any way we can do those defstruct/etc tests without digging through macroexpansions? i mean that's less a test of behavior and more a test that we haven't changed the code lately
20:33:54
Bike
should be possible to catch the warning. i think it's stable, since slime relies on it
2:20:11
drmeister
When we switch to faso mode - .o files become .faso files and .fasl files become .fasp files. Is this a good idea?
2:20:46
drmeister
An alternative is to keep the .o and .fasl extensions but internally they both get the .faso/.fasp file format.