Search
19:23:27
drmeister
https://www.irccloud.com/pastebin/cHLzbOu1/
19:23:28
Bike
i have made some minor changes to the analyzer's sif file generation already btw (in my branch)
19:23:32
Bike
there were brackets missing and stuff
19:23:45
Bike
so there are going to be some discrepancies
19:23:53
Bike
e.g. here you can see i have _Data in quotes
19:23:56
drmeister
And the .cc file has:
19:23:58
drmeister
https://www.irccloud.com/pastebin/NJNwBvrK/
19:24:11
drmeister
There should be a 1:1 correspondence here.
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:24:49
drmeister
I mean - should be generated from ...
19:24:52
Bike
(layout-offset-field-names end) and (layout-offset-field-names length)
19:25:04
drmeister
https://www.irccloud.com/pastebin/JdvOqtCm/
19:25:23
drmeister
Right - I agree - I think you caught a typo - good job.
19:25:58
Bike
well what i mean is, do i need to preserve both of those in the tag object?
19:26:31
Bike
do we sometimes have distinct "length" and "end" fields, or something?
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:26:58
drmeister
for GCVector there is a separate offset for "end" and "capacity"
19:27:46
drmeister
the cc file code is an array with the same number of fields on each line
19:28:14
drmeister
So I provide two offsets for GCVector, one for the "end" and one for the "capacity".
19:29:05
Bike
let's see... yeah, they're different in the cc. okay then.
19:35:12
Bike
i think that was the only major discrepancy. don't quote me on that though
19:35:34
Bike
"major" in the sense of making the generated code incorrect
20:42:26
Bike
generated code looks okay now, i think.
20:42:42
Bike
i guess i also need to generate the rest of clasp_gc.cc, like the namespaces and all
21:00:22
drmeister
Yes, we need to generate the rest of clasp_gc.cc
21:00:46
drmeister
We should be able to build the class hierarchy keeping track of the namespaces.
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:01:46
drmeister
C++ code generation sucks.
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
21:36:53
drmeister
Where is there a priority tag? I don't recall anything about them?
3:04:34
beach
Good morning everyone!
3:16:09
drmeister
I got the seqan extension to work in Cando with snapshot save/load and jupyterlab.
3:16:11
drmeister
https://usercontent.irccloud-cdn.com/file/elpEJwkN/image.png
3:57:54
drmeister
https://usercontent.irccloud-cdn.com/file/3hpxAFzS/image.png