freenode/#clasp - IRC Chatlog
Search
7:22:03
kpoeck
cl-bench-results are in https://gitlab.common-lisp.net/kpoeck/ansi-test/wikis/cl-bench-results-original
7:56:28
scymtym
drmeister: you asked about a CL implementation of the language server protocol. i have a simple one that i use for interfacing parser/compiler things with emacs
14:50:55
Bike
for asts it occurs to me that the parallel build is probably going to interact badly with our side effectual setup about inlining
16:06:38
Bike
side effects during load other than definitions are like, a few things in the compiler, and clos
16:08:04
Bike
i'd like to isolate the standard library (i.e. lsp) from the compiler. right now there are a few files that should basically be with the compiler (fli, direct-calls, backtrace) and then only some tiny things
16:15:21
beach
Did you find an explanation for the big performance difference between Clasp and CLISP?
16:16:18
Bike
no, but i figure a lot of it is that clisp is compiling to a cl-friendly bytecode, whereas clasp compiles to machine code.
16:16:55
Bike
and both of them are much slower than say sbcl, so cleavir generating poor code for itself is probably still a central issue
16:19:50
karlosz
i dont think generating poor code makes the compiler run slow. it seems much more like a microoptimization compared to genuine algorithmic slowness in the algorithms cleavir uses
16:21:11
Bike
the result you got with basic blocks is pretty interesting, so i'll probably give that a shot
16:21:51
Bike
the thing about bad code is that it's hard to see how cleavir would be generating code sufficiently horrible to be that slow, compared to compilers that don't optimize a ton anyway like ccl or clisp
16:23:36
karlosz
or when you can use basic blocks instead of instructions, since you typically have way less basic blocks than instructions