freenode/#clasp - IRC Chatlog
Search
13:25:26
Bike
i like the ir generated by my arguments parsing rewrite. clean. simpler to understand, i think. puts a lot more in llvm values. now if only it actually fuckin worked
13:37:27
karlosz
Bike: don't know if you got a note, but I did find a case in the wild where dominating definers don't exist for closure variables
13:38:04
karlosz
i fixed it by using lowest common ancestor in the dominance tree, so it shouldn't leave any undefined cells know
13:38:42
drmeister
In babel https://github.com/quicklisp/quicklisp-client/blob/master/dists/quicklisp/software/babel-20170630-git/src/strings.lisp#L96
13:38:46
karlosz
whenever you have time it would be great if you could spin up a build and see if it gets farther or not
13:42:10
Bike
basically it looks like there's a reference to the type (unicode-char *) somewhere, but that's not valid
13:57:48
drmeister
I just realized that the cl-jupyter code uses pzmq:bind and I was using pzmq:connect - I'll try switching to bind
13:59:44
drmeister
For some reason it thinks the argument is unicode (pzmq:bind worker "ipc://routing.ipc")
14:00:12
frgo
drmeister: The client uses connect to connect to a server socket that has established a listening socket using bind.
14:04:36
drmeister
frgo: I've got a really nasty bug that has knocked me on my butt for a week with a critical zmq message being dropped.
14:07:34
drmeister
I've got a DEALER -> ROUTER connection where the jupyter python middle-ware DEALER sends a kernel_info_request to the kernel ROUTER. The kernel gets the message and then sends a kernel_info_reply response. The response never makes it to the python middle-ware.
14:07:36
frgo
0MQ dropping a msg only happens when the protocol is violated in some way (that's what I have seen so far)
14:08:23
drmeister
The middle-ware doesn't provide a uuid identity - so zeromq creates a 5-byte identity with the form 0x0 w x y z where w x y z code a 4-byte random integer.
14:09:31
Bike
man llvm is really aggressive sometimes. i wrote in a comment that we could maybe generate a switch on the number of args for &optional, and llvm just takes my shitty series of conditions and makes a switch out of it