freenode/#clasp - IRC Chatlog
Search
4:50:44
drmeister
Lang Hames (Apple software engineer and developer of the ORC JIT) just added what should be the last thing that we need to switch to ORCv2 on linux.
4:51:49
drmeister
I'm in process of testing it. If it works - then the path should be clear to image save/load.
4:52:54
drmeister
Also, we should be able to switch back to the small code model and switching away from that when we switched to faso files had a large impact on stack unwinding speed.
4:53:43
drmeister
We've bypassed stack unwinding with C++ exceptions in many important cases. But the ones that we couldn't get away from should improve now.
14:21:24
drmeister
I got clasp building against llvm12 pulled last night with Lang’s new changes for jitlink and linux.
14:21:54
drmeister
Testing it failed on Linux so I sent him the module and object file that broke it.
14:22:27
drmeister
Currently in the future branch aclasp and bclasp build and run. Cclasp is broken.
14:24:08
drmeister
I’ll implement the new code gcing and then I’ll fix backtraces and then I’ll tackle cclasp
14:43:00
drmeister
Bike - backtraces are broken. The name of the functions in the backtraces are wrong. I’ll dump and example.
14:43:43
drmeister
It means the function that takes a return address and returns a function name is broken - right?
14:50:46
Bike
this is in your branch, right? maybe the template stuff you put in involves actual pointers
14:52:52
drmeister
Going forward we should have just two ways to search symbols. 1. executable/libraries 2. object files in memory from jitting, faso files and image save/load.
14:55:17
drmeister
operating_system_backtrace calls the operating system 'backtrace(buffer,num)' facility.
15:09:55
drmeister
We create a std::vector<BacktraceEntry> - BacktraceEntry is a low level C++ object, not exposed to Common Lisp. We fill it with everything that we can get.
15:10:34
drmeister
Then we copy the info into Frame_O objects, cons up a list of them and pass them to a callback using (core:call-with-backtrace ...)
15:11:09
drmeister
That way it's clear what is in the backtrace. Everything above the callback is in the backtrace and everything below it is not.