freenode/#sicl - IRC Chatlog
Search
13:04:47
Bike
RECOVER could probably just be CONTINUE, which is the standard "keep going in a default way" restart
13:04:47
Colleen
Bike: drmeister said 24 minutes, 33 seconds ago: Currently llvm loses a lot of information about local variables at -O3. I thought if at high debug we mark all loads and stores in a function as 'volatile' that this would keep the variable in memory even at high optimization and I would have a hope of pulling it out of the dwarf debug info. There would be a runtime penalty of course. Then when/if llvm's ability to track variables improves we drop volatile.
18:57:33
Bike
https://github.com/robert-strandh/SICL/compare/cst-to-ast-errors?expand=1 here's what i've done so far with the conditions stuff
18:58:05
Bike
i've got it coordinated enough with clasp that normal slime things like compiler notes work, and it'll go to the position of a handler-bind macro form with bad syntax, and such
19:49:15
Bike
i decided a resignaling restart wasn't necessary, the client can just do it at the higher levle if they want