17:04:21drmeisterUsing clasp-cleavir:cleavir-compile-file is the least crashy way to test things. Cleavir will do its thing and generate llvm-ir and write it out to a file.
17:05:15drmeisterAs long as there are no compile-time side effects
17:05:35drmeisterThen we can check the llvm-ir at our leasure.
19:08:35Bikeit doesn't compile, but it just errors instead of segfaulting, so that's nice
19:12:53Bikehm, it's a cleavir internal problem too
19:13:15Bikewe haven't had an instruction with multiple successors and an output that's closed over before
19:18:12Bikei guess we kind of need to special case it anyway due to its odd control flow
19:22:03karloszdoes it make more sense to use HIR or MIR as a backend for generating bytecode for a stack machine?
19:22:44Bikemir is supposed to be what's used for that regardless of the target
19:22:51karloszi could hack up the hir interpreter to produce clisp bytecode instead, but it seems like mir would be more suited for address calculations etc