freenode/#sbcl - IRC Chatlog
Search
13:55:32
scymtym
stassats: (compile :node/lvar :derive-type :misc.4) in compiler.pure.lisp started to fail because a WARNING is signaled now (used to be a STYLE-WARNING)
14:29:28
stassats
in other test news, nlx-causes-alien-stack-leak started failing on -c-stack-is-control-stack
14:30:42
stassats
;; No need for unwind protect here, since allocation involves modifying NSP, and NSP is saved and restored during NLX. And in non-transformed case it performs finalization.
14:34:41
stassats
that's an incorrect assumption, if i THROW from within with-alien, the CATCH will indeed restore NSP, but not a return-from
14:40:34
stassats
but this is basically akin to UNBIND, no full blown UWP needed, because of the stated reasons
14:44:31
stassats
if done right, even the non NLX case will get faster, since multiple NSP restores can be rolled into one
21:48:48
stassats
rethinking the whole approach, instead of trying to make a really specific nsp-protect, maybe i can have simple-unwind-protect, which acts like special bindings, without establishing catch or unwind blocks, just executing code on RETURN-FROM