freenode/#clasp - IRC Chatlog
Search
3:40:59
drmeister
Bike: With DWARF - do you recall how to get the start and end of a function given a sectioned address?
3:57:11
drmeister
I'm still working on backtraces. I'm going full on DWARF and eliminating some of the old ways I would dig out symbols.
5:29:20
drmeister
::notify Bike The future branch is now open for business. On bigmac you use the llvm in /opt/llvm-project-tot. bclasp builds but cclasp fails in inline.lisp. If backtraces are still not up to snuff in slime we can switch things over to use DWARF to interrogate the stackmaps and get rid of the old stackmap recording/searching mechanism.
6:37:29
drmeister
::notify Bike The next release of MMTk will be coming out in two weeks and Steve Blackburn expects we should have immix within 4 to 6 weeks. He's interested in developing conservative GC that looks like the following (I'm posting a link to one of his papers - I haven't read it - but will soon).
7:22:46
no-defun-allowed
Is RC Immix the only incremental Immix? I guess the numbers can't lie about how they optimised deferred refcounting, but you now have the cycle-breaking full collections to fear, in place of your usual major GC.
13:26:47
Colleen
Bike: drmeister said 7 hours, 57 minutes ago: The future branch is now open for business. On bigmac you use the llvm in /opt/llvm-project-tot. bclasp builds but cclasp fails in inline.lisp. If backtraces are still not up to snuff in slime we can switch things over to use DWARF to interrogate the stackmaps and get rid of the old stackmap recording/searching mechanism.
13:26:48
Colleen
Bike: drmeister said 6 hours, 49 minutes ago: The next release of MMTk will be coming out in two weeks and Steve Blackburn expects we should have immix within 4 to 6 weeks. He's interested in developing conservative GC that looks like the following (I'm posting a link to one of his papers - I haven't read it - but will soon).
14:10:48
drmeister
I don't have arguments in backtraces switched over to use the object files yet - so they may not work.
14:12:30
drmeister
The idea now is that there will be a single list of ObjectFile_O objects and each one points to a Code_O object. The ObjectFile_O object gives us DWARF and the Code_O object keeps track of the .text sections (relocated code) and .stackmaps
14:13:36
drmeister
In the future we could change the ObjectFile_O objects to leave them on disk and only mmap them when we need to scan them.
14:15:27
drmeister
We can leave faso files on disk for things like quicklisp code and image code and only keep the object files for code we ourselves JITted. I think in the image save format I'll set the object files up so we mmap them.
14:34:29
drmeister
The llvm::MemoryBuffer class supports mmap'ing from files and it supports representing blocks of memory in memory.
14:35:41
drmeister
So an ObjectFile_O object will basically preside over an llvm::MemoryBuffer that represents a unix object file and that can exist in memory or on disk.
14:36:21
drmeister
The image save/load format will put all the live object files into one image and use mmap to search them.
14:42:02
drmeister
I'll need to rearrange the filenames in src/llvmo and clean it up. What they do now barely matches the source filenames.
14:43:57
Bike
when building i get "Cannot find the external symbol FUNCTION-INFO-REFERENCE-INDEX in #<PACKAGE COMPILER>" while loading/compiling translate.lisp
14:44:34
drmeister
When building iclasp or aclasp or bclasp everything just worked. Where are you seeing this?
14:48:43
Bike
this looks like a merge failure https://github.com/clasp-developers/clasp/blob/future/src/lisp/kernel/cleavir/translate.lisp#L526 a function by that name is called here, but it doesn't seem to be defined anywhere.
14:58:01
drmeister
But this is triggering another memory - I think I need to fix something else - checking...
15:11:06
Bike
When calling MAKE-FUNCTION-INFO with the lambda-list (&KEY FUNCTION-NAME LAMBDA-LIST DECLARES SPI) the bad keyword argument :FORM was passed
15:27:52
Bike
okay, so now the problem is that a call to irc-create-invoke-wft gets NIL when it's expecting an array (a string, maybe?)