libera/#clasp - IRC Chatlog
Search
14:20:52
Bike
alternately, we could rely on bytecode_vm itself not signaling errors, and just look through the VM call stack, maybe. but i'm not sure how it would be combined with the machine call stack.
14:24:10
Bike
because i have a scheme in mind for how to record source info for bytecode, so sldb v would work, but it's useless if we can't get it in the debugger.
19:00:57
Bike
tried a flame graph for the bytecode swank load - works fine. i don't understand the results, though. says it's spending a lot of time in dispatch miss, but i don't know why it would be taking the slow path. kinda worrying!
23:04:35
Bike
think i managed to shave about a second off the bytecode slime startup with a small rearrangement of the fasl format. so i'm feeling optimistic about further optimizations.
23:46:26
cracauer
Wait, the right dir already is in llvm-config14 --ldflags but the build seems to ignore it.
0:08:15
Bike
but there's also an underlying issue of everything dispatch missing for some reason, so i'll probably have to dust off the fastgf log
0:08:39
Bike
and maybe come up with something more focused. it would probably be helpful to tell _some particular gf_ to log dispatch miss stuff. i'll probably try writing that
0:09:15
Bike
debug-fastgf was basically written for debugging fastgf as a whole, so it's probably not good for performance telemetry