Marek Chalupa
Marek Chalupa
Hi, it's a good question, I guess it's a bug (frankly, I do not remember why I wrote it like this, it's quite old code and I hope I will...
> **Problem:** The code wouldn't compile (s and v are not declared) and s isn't relevant to A. The code generated by `llvm-to-source` is not meant to be compilable. This...
> Sorry for the dumb question, but is there any other type of instruction beyond declaration that will not be picked up by llvm-to-source? Probably yes, but hard to tell......
Hi, actually, this is one of the extensions that I would like to do in the future, I just do not know when I'll get to it. You need to...
Of course, if you would be interested in providing patches and just need a starting point, I can help you with that.
Although 1. would be more generic (you could continue working with the cloned module as you would have all the results mapped to this module), it is more complicated and...
You should be able to get which parameters are relevant from the dependence graph, so yes, you can use DG to find that out.
By getting the information from the dependence graph I meant to use the API of `LLVMDependenceGraph` and `LLVMNode` from C++ (but it would be probably also possible to parse the...
And is the declaration present if you skip slicing? That is, just compile the code to LLVM and then (without slicing) use your tool to generate the source code?
> And what if I need both forward and backward slice , what arguments should I use ? The forward slice in DG does backward slicing to make the slice...