libera/#clasp - IRC Chatlog
Search
0:34:17
yitzi
I had to make the jupyter installer and snapshot scripts use the fasl output translation folder inside the build directory like the analyzer does. Now I can build cando in one build folder and clasp in a different one both in the same git repo.
0:46:24
Bike
if the problem is just contention i don't know if lock free tables would improve things much
0:46:24
Colleen
Bike: drmeister said 1 hour, 2 minutes ago: Good going - yes - I think we don't make them thread safe by default because that slows them down.
1:20:39
Bike
you still get contention if you just have multiple threads accessing memory with the same cache lines, right?
1:24:13
Bike
well, hopefully. it's still going. seems very slow, like slower than the serial version
1:31:04
Bike
i mean, this one is just a cache, and it's for different filenames, which might not be shared between threads either
2:19:43
Bike
memoized-probe-file is the one i just put the lock on, that i think could probably be thread local given that it's just a cache, but there are several more throughout clasp analyzer that i do not understand
11:40:26
yitzi
Not yet. Trying to get through dcando. I am running it in a docker instance on my own machine and killing the workflow when I find an issue. So at least it doesn't take 5 hours to know if there is an issue. I think we will have something soon.
11:41:27
drmeister
What is the approach with quicklisp now? Where is the code that sets up all the dcando dependencies?
11:43:26
yitzi
A custom clasprc file is used during the build that loads quicklisp from the build directory. It adds quickclasp also. The extension loading mechanism looks for quicklisp and if it is found it uses QL:QUICKLOAD, otherwise it falls back to ASDF:LOAD-SYSTEM (which is used by clpm).
11:44:28
yitzi
I've removed the code that I was working on to create snapshots in the user's `~/.local/bin/` and avoid setting up quicklisp in the build directory. I'll delay working on that until after the debian packages work.
11:47:04
yitzi
It is generated by koga into `/build/boehmprecise/`. Look in `src/koga/scripts.lisp` at the bottom.
11:52:21
yitzi
If you checkout the ext-load branch and run koga you should be able to see it in `/build/boehmprecise/` or whatever the variant name is.
11:53:31
drmeister
https://github.com/clasp-developers/clasp/blob/ext-load/src/koga/scripts.lisp#L143