Marek Surovič

Maybe the LLVM IR linker API might be of some use here: http://www.llvm.org/doxygen/classllvm_1_1IRMover.html (Move IR from one module to another) http://www.llvm.org/doxygen/classllvm_1_1Linker.html (Link a module into another) http://llvm.org/doxygen/Cloning_8h.html (InlineFunction and CloneModule)

I think we don't need to explicitly use `llvm-dis` for this, the roundtrip tests should be enough, because they call `clang`. The recent issue we had is more about the...

> I think we should also look into how people have tried to automate instcombine rules. There's probably a whole lot of work here. Yeah, there's defintiely a ton of...

LLVM has a nice [single source](https://github.com/llvm/llvm-test-suite/tree/main/SingleSource) [test suite](https://github.com/llvm/llvm-test-suite). also GCC has it's [torture test suite](https://github.com/gcc-mirror/gcc/tree/master/gcc/testsuite/gcc.c-torture/execute).

>foo.bc.zip As a quick workaround, one can run `opt -lowerinvoke foo.bc > foo.opt.bc` as preprocessing. `rellic-decomp` will produce bitcode afterwards. This is not to be taken as a solution to...

How does the input LLVM IR look like? We need to remember that we're not in the business of roundtripping C code. Rellic produces C from LLVM IR in a...

> The future of anvill-produced bitcode may also include LLVM debug information metadata, and so gaining first-class support is key. Agreed. My point mainly here is that if we get...

Resolved by #121 Unfortunately I haven't found a good way of regression testing this one using our executable roundtrip tests, because we don't have type inference.

I think it is important to be able to handle as much of LLVM IR as possible. That means lifted bytecode (anvill, remill, mcsema) as well as bytecode compiled by...

This has been partially solved by #106 . Keeping this open though.