freenode/#clasp - IRC Chatlog
Search
19:07:14
drmeister
After the last week of changes and addition of an LLVM-IR rewriting pass to move activation frame variables into allocas and registers - I expected a big win.
19:08:46
drmeister
So - overall, the improvement in performance is almost perfectly balanced by the increased time spent optimizing things.
19:09:47
drmeister
Now the good news is that these last changes sweep away a lot of old code and consolidate code.
19:10:25
drmeister
So now I have an easier time improving method calls. That should be a win in both bclasp and cclasp with no additional overhead.
19:52:45
frgo
Hi Shinmera. I had been readimg your blog post https://reader.tymoon.eu/article/357 and noticed that the link for Harmony (https://shinmera.github.io/harmony) goes into nowhere land.
21:25:13
drmeister
ACTION doesn't need self aware AI's to make his life miserable. The stupid computers of today do a fine job.
21:32:53
drmeister
It looks like I've introduced another threading problem in the past week. I'm wracking my brain to try and recall what it could be.
21:33:34
drmeister
When I set preferred-communication-style in clasp.lisp to NIL slime starts up fine.
21:55:15
drmeister
Bike - in case you didn't see the log from the last hour - slime works if you set the preferred-communication-style to NIL.
21:56:26
Bike
so it does. well, on the bright side, things can be made to work, though on the downside, t hreading problems
21:56:38
drmeister
I can't recall what it was - but I don't want to be derailed at the moment - I'm working on method calls.
21:57:20
Bike
i already had a branch set up for my sandbox stuff, so i was just going to use that tomorrow. it's building right now
21:58:05
drmeister
I mean - I can't recall at the moment what I might have done that introduced a threading problem. I'll keep thinking on it.
21:59:03
drmeister
Emacs has frozen up like that half a dozen times - every time it was a threading issue.
23:33:08
emaczen
drmeiseter: All I want to do is something like the lisp method #'start-capturing at the bottom: http://paste.lisp.org/display/358268
23:34:02
emaczen
but Instead of CFFI I want to use Clasp because the C++ api is better/easier to deal with, and if Clasp has some conversion mechanism between the STL then what I want to do should be a piece of cake
23:38:32
emaczen
https://docs.opencv.org/3.0-beta/modules/imgcodecs/doc/reading_and_writing_images.html -- I really want to use the C++ function imencode rather than the equivalent C function cvEncodeImage
23:53:00
Bike
i don't work with that part, drmeister is better equipped to answer. but yeah there's https://github.com/drmeister/demo-clasp-cxx and https://github.com/drmeister/demo-bullet
0:14:41
drmeister
emaczen: If you are familiar with boost::python or luabind - those are two C++ template libraries that create bindings between C++ and Python and Lua respectively.
0:17:04
drmeister
Clasp uses these facilities to interoperate with the llvm C++ library and the Clang ASTMatcher library - as well as the Clasp C++ runtime. Thousands of functions and hundreds of C++ classes and methods and dozens of enums are exposed this way.
0:20:16
drmeister
The issue is we hack the X86-64 calling convention - although I might be fixing that soon.
0:20:57
emaczen
I didn't configure anything though and I think there are different JVMs you can install just for these purposes too.
2:41:22
drmeister
Waaaaaay back - when I was first developing Clasp. I'd run in emacs using 'run-lisp' and the *inferior-lisp* buffer.
2:42:30
drmeister
I'm glad that the last weekend put several nails in the coffin of the idea of writing a new bclasp compiler.