libera/#sbcl - IRC Chatlog
Search
16:48:59
|3b|
flip214: out of curiosity, is it any faster if you (check-type count (unsigned-byte 31))?
16:57:33
|3b|
on my machine, loop overhead is about 1 sec for 500M if it is doing generic math for the loop counter
16:58:02
|3b|
ACTION is too lazy to actually build the shared lib though, so not sure how that compares to whole thing
18:52:23
|3b|
(and even if it did handle windows transparently, i should be working on other things anyway)
19:09:25
|3b|
flip214: i wasn't so much thinking of the marshalling stuff they mention on hn as what we see in CFFI where it just can't do that in the portability layer, so drops to libffi for "complicated" calls
19:12:26
|3b|
which would be interesting to know since then i'd know whether to complain to sbcl "everyone else can do this well" or complain to C libs "hardly anybody can do this well"
23:44:38
Nilby
|3b|: not having stuct by value makes it nearly impossible for anyone else to build my software on windows, even on unix it's trouble require os packages from asdf
0:18:23
hayley
How does a major GC work in gencgc? I can see that old->new pointers are handled by card marks (or write protection), but what makes new->old pointers work? Say, if we collected generation #1, how are 0->1 pointers fixed?