libera/#clasp - IRC Chatlog
Search
3:37:35
Bike
haven't looked in detail. they didn't seem especially serious. one was that i made changes to wscript, which has been deleted in main. easy to resolve.
6:23:12
drmeister
::notify Bike I tried your sjlj branch and ran perf top watching the process. I don't see UnwindFind_FDE in the top 20 functions. It used to be the top with >90% of the time spent in UnwindFind_FDE
10:26:53
Colleen
yitzi: drmeister said 6 hours, 50 minutes ago: I fixed all the compile errors with --source-debug
13:31:59
Colleen
Bike: drmeister said 7 hours, 8 minutes ago: I tried your sjlj branch and ran perf top watching the process. I don't see UnwindFind_FDE in the top 20 functions. It used to be the top with >90% of the time spent in UnwindFind_FDE
13:35:40
yitzi
I compiled with `--source-debug` and it worked. I think drmeister got all the fmt stuff fixed.
13:39:59
yitzi
I am getting some "unexpected failures" in ansi-tests on that CI testing PR. Has anybody run ANSI tests lately?
13:41:42
yitzi
You can also look at https://github.com/clasp-developers/clasp/runs/6385903554?check_suite_focus=true
13:42:26
drmeister
I ran the static analyzer on main yesterday - I'll hold off pushing anything until Bike pushes his changes.
13:43:16
yitzi
I we can get a clean run of ANSI tests then that PR can be merged and we can get CI testing on GitHub!
13:44:29
yitzi
Yeah, its weird. I thought they were clean. Hoping koga hasn't jacked a compilation option.
13:47:28
drmeister
Bike: When I was playing around with sjlj-unwind I couldn't see UnwindFind_FDE taking any time at all.
13:47:58
Bike
yeah, i think i got just about everything in C++ that calls lisp, and a good fraction of the C++ that signals errors
13:49:43
drmeister
I got borodust's claw-usb to work well enough to give me a list of all attached USB devices.
13:50:26
drmeister
It uses a C library called libusb - it should be pretty straightforward to use. It's refreshing to use a simple C API.
13:51:55
drmeister
I'm getting a RFID printer in a couple of days. My plan is to figure out how to print RFID labels with the libusb API.
13:59:07
Bike
should all uses of the BF macro be gone? there are a few here, but they're not compiled https://github.com/clasp-developers/clasp/blob/main/src/core/evaluator.cc#L1866-L1881
14:00:49
drmeister
I'm stiff and sore and feeling old this morning. But I have a simple three step plan to fix things - it involves Cando and libusb.
14:06:38
drmeister
Bike: This is what I normally get when I run `perf top` when cclasp is building and loading/compiling inline.lisp and later files...
14:07:50
drmeister
At the risk of repeating myself - yesterday, with sjlj-unwind - I couldn't see it in the top functions.
14:14:32
drmeister
For reference later, building ASDF: Time real(51.441 secs) run(51.441 secs) consed(3907625424 bytes) interps(547) unwinds(6138)
14:15:56
Bike
there might be some failures in obscure bits of ansi tests. yesterday i realized i screwed up one case of progv because we happened to have it in our tests, but it never came up in just building clasp and cando
14:18:44
Bike
anyways, so right now i'm running the analyzer, and that's gonna take a while. if possible it would be convenient if there were no more commits to main until i finish up here
14:34:25
yitzi
I am wondering if we should call the snapshot versions of cando `scando` instead of `dcando`. (or `cando-snapshot`) Yes they normally get made in the d stage, but in the "user based" installer I am contemplating that is confusing. Users don't really know what the stages are.
14:38:14
yitzi
In the scheme I am trying out the package based installers don't build the d stage. Instead there is an script that the user can run like this `clasp-user-install --snapshot-cando --jupyter`
14:39:26
yitzi
This would make a snapshot of cando using their quicklisp installation into `~/.local/bin/scando` and then create a jupyter kernel for it at `~/.local/jupyter/kernels/scando/`
14:41:41
drmeister
I'm running the ansi-tests and watching `perf top -p <pid>`. _Unwind_Find_FDE swings from a few percent to over 80% as we go from test to test.