Andrea Jemmett
Andrea Jemmett
I understand. If the version of LLVM+SVF which was used to do reachability analysis for the evaluation in the papers (both Beacon and Titan) is unknown, then how do you...
Forgot to mention: also the option to debug the errors that come up by using LLVM 15 (as I've done for what was initially described in this issue) is infeasible.
So I don't need to use `icfg_index.py`?
If I use `icfg_index.py`, which version of LLVM and SVF have been used for the paper evaluation to generate the ICFG `.dot` file to feed to it?
That would be ``` LLVM: 4.0.0 SVF: commit 3170e83b03eefc15e5a3707e5c52dc726ffcd60a ``` But then I wonder what is the point of using `icfg_index.py` instead of the reachability analysis done by `precondInfer`? Both...
Thanks that clears it! How about the evaluation in the Titan paper? Have you used the same version of LLVM and SVF as Beacon's paper to generate the ICFG for...
Do you have a rough estimate of when you can make at least the MAGMA compatibility changes available? Otherwise I'll have to start my evaluation of Beacon on MAGMA as...
Okay, I'll do that. To recap, I'll evaluate Beacon on MAGMA by doing reachability analysis with `icfg_index.py` and using the ICFG generated by LLVM and SVF with the version as...
I'm sorry, can you please be more specific?
> I'll evaluate Beacon on MAGMA by doing reachability analysis with `icfg_index.py` and using the ICFG generated by LLVM and SVF with the version as specified in this repo and...