libera/#clasp - IRC Chatlog
Search
17:05:55
Bike
with my generated clasp_gc.cc, aclasp built successfully, but bclasp gets me a stupid type error in CLOS
17:10:51
Bike
hm, but in the analyzer-generated clasp_gc_cando.cc, the highest-stamp class has the same stamp number as STAMPWTAG_max, and so does the stuff i have the scraper generating
17:12:51
Bike
"global_NextBuiltInStamp starts at STAMPWTAG_max+1", that seems fine (although it's "global_NextUnshiftedStamp" now i think)
17:13:37
Bike
does it need to have a max wtag? i have a max stamp of 1535, which obviously has 01 at the end, not 11
17:33:37
Bike
er, this time it worked maybe...? maybe i just needed to clean before building and everything's fine
18:01:06
Bike
that is, i can manually direct the scraper to generate a working clasp_gc.cc from clasp_gc.sif, though i'm not sure about the table thing i mentioned
19:37:30
drmeister
It will be a temporary generated file - right? We can put it in build/<GC>/generated/
19:51:11
Bike
right now i just have a function that outputs a string, and i've been writing it into src/main/clasp_gc.cc, so i haven't had to adapt the build
20:01:45
Bike
is there any way i could validate whether the deallocators/finalizers are working correctly? I think you said they're both sort of obscure features?
20:04:28
drmeister
For the finalizers - you could generate a printf statement in every finalizer and then watch them print when you run clasp.
20:04:55
drmeister
You can target it by looking for classes that use finalizers - like Stream_O (I think). Hang on.
20:05:32
Bike
i don't know how these tables are accessed is all. they're jused for jump tables but i don't know if they're indexed by stamp or what