freenode/#clasp - IRC Chatlog
Search
15:36:02
beach
I don't get it though. If you can detect the situation and replace the unwind with an illegal unwind instruction, how come it is not possible to avoid inlining when that situation is detected?
15:37:26
karlosz
you would have to look inside every function to see if it odes anything weird before you start the inlining process to fix it
18:20:15
frgo
Guys, where can I find a PDF detailling Cleavir? I need to read up on some of its features ...
19:43:20
Bike
ok. got a bug or something in sicl. if you run segregate-lexicals, sometimes it will want to turn a function parameter into a cell. when it does it knocks the enter-instruction's lambda-list and outputs out of sync. and i'm not sure it results in something sane, either, let me check
19:47:53
Bike
ok, the generated code is sane actually. so it's just the lambda-list/outputs mismatch.
19:51:27
karlosz
okay, thanks. how long does it take to build clasp on the hardware you have? i have a new laptop, yet i still takes about 4 hours to build clasp
20:09:40
karlosz
maybe it would help catch bugs if we had an ir consistency checker that just makes sure everything is what they should be
20:10:01
karlosz
like checking successors, inputs, using-instructions, etc... are all what they should be
20:11:34
karlosz
i can imagine a verifier for closure conversion that tests whether any location is used by a function that doesnt own it, for example
20:18:17
karlosz
yeah, it probably makes sense to program different consistency checks individually. usually they can be associated with some pass, like checking successors and predecessors agree like for cleavir-ir:set-predecessors
20:18:40
karlosz
could also be used to empirically determine whether we need things like reinitialize-data and set-predecessors after certain passes
20:52:48
drmeister
karlosz: I'll be able to give you more of a hand there once I get done what I'm working on now.