libera/#clasp - IRC Chatlog
Search
4:31:08
Bike
i finally did the one last bytecode compiler optimization that was on the list, and now i can compile+load swank in less than seven seconds. however... with --norc it's a little under 3.5s. i'm only turning on the bytecode compiler after the rc file loads, so loading quicklisp is a good half of the time apparently.
4:33:33
Bike
as for where the actual compiler is spending its time... flame graph is marginally helpful since it's deeply recursive (same old story) but the actual perf report is fairly clear
4:34:33
Bike
building inline ASTs for cleavir is still taking a ton of time... there's some arithmetic stuff that i'd like cleavir to be able to optimize but which will require some pretty serious changes... we might want to do some instruction-level profiling on the bytecode_vm function and others, like karlosz was doing earlier
14:20:18
Bike
mm, you ran the static analysis again... i had to do that too, but that's fine, your changes should go in first
14:21:45
yitzi
Yeah. I probably should have made that a separate commit in case there were conflicts.
14:49:46
selwynning
i was thinking more along the lines of compiling individual functions to wasm by making use of clasp's compiler to llvm
14:50:12
selwynning
i don't necessarily need the entire lisp compiler or even much of ansi to be present in what i deploy
14:53:49
Bike
clasp is not really built with the idea of having functions run freestanding like that.
15:41:25
yitzi
Bike: I just reverted return of -1 in set_column and made it return the column value directly. This match set_position, etc. vs making set_column return void.