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:09:51|3b|and wondered if other FFIs have similar slow paths
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"
19:44:02|3b|hmm, *disassemble-annotate* T breaks disassembly of code using #+#.(foo)
23:44:38Nilby|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:23hayleyHow 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?
0:20:11hayleyHm, I guess all of generation #0 would be raised to #1 beforehand.
0:27:24hayleySo there are no #0 -> #1 pointers, since there are no #0 objects. Well then.