libera/#clasp - IRC Chatlog
Search
11:01:56
yitzi
My changes to project_headers has broken the nightly builds b.c. those use absolute paths during building. Working on a fix.
11:41:26
yitzi
The normal build and analyzer should be fine. It is when one does a "reproducible build" in which koga replaces the build path names with the destination installed pathnames.
13:02:41
Bike
i'll want to improve the vm disassembler before doing that, like making it print textually and doing labels
13:24:54
Bike
you'll have to do (vm::disassemble-bytecode (core:bytecode-module/bytecode (core:global-entry-point-code function-goes-here)))
13:34:29
Bike
ok, pushed to vm/main so that it will let vm:disassemble work on bytecode entry points, i think
14:38:22
drmeister
Good thing cell elision is working - and this is a reminder of how Common Lisp works.
14:40:36
Bike
we could soup up the compiler to do the very basic optimizations required to eliminate that, like reducing - to two-arg--
15:33:31
Bike
Yes, but given a bytecode module there's no way to get the entry points into it, I don't think
15:41:00
drmeister
Do you get the module and then disassemble that without considering the entry point?
15:41:41
Bike
Yes, and even if we were disassembling from an entry point, it would be nice to display all the entry points, so you could see where any local functions are etc
15:47:26
yitzi
drmeister: There is a docker build for clasp and one for cando-demos. They are weekly.
16:03:52
Bike
By the way, it looks like even in the existing interpreter, macrolet uses ext:parse-macro, which is written in lisp, to come up with macroexpanders. So if we want the bytecode compiler to be complete and in C++ we will have to rewrite parse-macro into C++
16:18:08
Colleen
karlosz: Bike said 15 hours, 13 minutes ago: the env structures replace the ones in compile.lisp. i pushed how it looks in the clasp branch of cvm (didn't want to make main even messier than it was)
16:18:08
Colleen
karlosz: Bike said 14 hours, 52 minutes ago: they were written in anticipation of the eventual port of the compiler to C++
16:21:27
drmeister
I moved the side stack to the top of the main stack. It's directly contained within the VirtualMachine class.
16:40:13
yitzi
We don't depend on specific version of fmt. But it may have been linked with v8 b.c. the build was older then the current version. The new build should use v9.