Search
Wednesday, 21st of July 2021, 6:26:16 UTC
13:00:56
Bike
Lisp_O is apparently counted as a "class" rather than a "gc managed type" which is screwing a few things up
13:01:03
Bike
trying to generate a typeq test for it and stuff
13:01:21
Bike
i guess it does need a stamp to be gcable
14:03:48
Bike
i guess i can look at the root class
14:04:10
Bike
does an AstVisitor_O need a typeq test? i guess probably?
14:28:24
Bike
now it seems to just die when iclasp starts. okay.
15:17:15
Bike
having the scraper generate STAMPWTAG_null stuff seems to crash the normal build, but if it's not there the precise build crashes
15:18:26
Bike
not sure what i'm missing here
15:20:52
Bike
actually no, what is even happening here
15:36:31
Bike
oh, i see, it's another definition that's different between scraper-generated and analyzer-generated code even though they're the same thing
16:53:36
drmeister
How are things going? Anything I can assist with?
16:54:34
Bike
i think i figured this out, but i guess if you could confirm that AstVisitor_O needs a typeq test and Lisp_O doesn't
17:04:36
yitzi
drmeister: posted a gif over in chat showing a JupyterLab debugging session. Just FYI.
17:41:48
drmeister
AstVisitor_O does and Lisp_O doesn't.
17:42:05
drmeister
Why isn't AstVisitor_O in the T_O hierarchy - looking...
17:42:39
Bike
it's in the one you said was weird yesterday
17:45:16
drmeister
It is weird. I think we should get rid of it.
17:46:01
drmeister
It was my first attempt at walking the clang AST and then I discovered the ASTMatcher stuff and forgot about it.
17:46:18
drmeister
So - it's going to mean removing the header file(s) and the astVisitor.cc
17:46:28
drmeister
So yeah - get rid of it.
18:19:08
Bike
ok yeah, back to dying silently right after iclasp dies
18:19:32
Bike
i get the "There are DEBUG_xxxx" messages and then it's all waf failures
Wednesday, 21st of July 2021, 18:26:16 UTC