libera/#clasp - IRC Chatlog
Search
19:19:28
Bike
i mean, conceptually. i don't get how the corresponding c++ code really defines anything
19:20:01
Bike
{ TAGS:VARIABLE-CAPACITY (( TAGS:CTYPE . "unsigned short")( TAGS:OFFSET-BASE-CTYPE . "gctools::GCArray_moveable<unsigned short>")( TAGS:FIELD-NAMES . ("_Data"))) \
19:20:43
Bike
this is incorrect, as far as i can tell, because the field name for the capacity is _MaybeSignedLength, and that's what's in clasp_gc.cc too
19:23:28
Bike
i have made some minor changes to the analyzer's sif file generation already btw (in my branch)
19:24:32
drmeister
{ variable_capacity, sizeof(short), __builtin_offsetof(SAFE_TYPE_MACRO(gctools::GCArray_moveable<short>),_MaybeSignedLength), __builtin_offsetof(SAFE_TYPE_MACRO(gctools::GCArray_moveable<short>),_MaybeSignedLength), 0, NULL },
19:24:40
Bike
in the code generator it actually uses two things which apparently both end up as _MaybeSignedLength
19:26:39
drmeister
This is an array - that means the "end" and "capacity" are equivalent and I put the same info in them.
19:28:14
drmeister
So I provide two offsets for GCVector, one for the "end" and one for the "capacity".
21:01:32
drmeister
The GC_DECLARE_FORWARDS part of the clasp_gc_cando.cc was a especially annoying thing to have to build.
21:36:16
Bike
drmeister: this isn't important, but out of curiosity, what are priority tags for? i think there's only one use in the codebase
3:16:09
drmeister
I got the seqan extension to work in Cando with snapshot save/load and jupyterlab.