freenode/#clasp - IRC Chatlog
Search
15:35:25
drmeister
Bike: Do you know if in our compiled CL code - do we ever modify anything other than the literals vector within the globals of a Module?
15:35:47
drmeister
But if we do - I need to save that as part of the image save so that I can restore that state on load.
15:37:15
drmeister
What that means is do we create any llvm global variables within the module and modify them other than the ones that I set up?
15:39:22
drmeister
Code_O objects collapse to much smaller objects in the save/load image because they only carry their literals into the image.
15:40:33
drmeister
ObjectFile_O objects add a unix object file to the image. I'm adding them at the end in a list and each object file will be page aligned. It will be just like a FASO file. Then later I can figure out how to leave things on disk and only mmap them in when we need them for backtraces.
15:40:59
drmeister
Also, quicklisp compiled code object files will ultimately be left on disk. Only JITted object files will remain in memory.
15:41:54
drmeister
Yeah - I don't think we have any. You can see them in any .ll file generated by clasp.
15:47:22
drmeister
I'm initializing everything in place in the loaded image before allocating any of the objects in the gc. A lot of my template code doesn't work because the headers aren't set up properly.
15:58:23
drmeister
Actually no - they shouldn't - but some things are being clobbered in places that I don't expect.
15:59:12
drmeister
I keep harping on time traveling debugging - but it's really helpful here. I can put a watch point on anything that has the wrong value and then reverse continue to the point where it changed to the wrong value.