Classification of Transformers? #23
Closed
Labels
Comments
|
Redex and Sparta are definitely static analyzers, not dynamic. |
|
No hard opinion either way. Profile guided optimizations require execution - so dynamic. eBPF is dynamic? How about Souper? |
|
Hey @chadbrewbaker, |
|
This issue has been automatically marked as stale because it has not had recent activity in the last 60 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
|
Merged those tools. Thanks for the recommendation @chadbrewbaker. Please keep 'em coming. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm calling them transformers for lack of a better term:
https://github.com/google/souper - optimize LLVM IR with SMT solvers
https://github.com/facebookincubator/BOLT - profile guided permutation of linking to improve cache efficiency
https://github.com/google/llvm-propeller - profile guided hot/cold function splitting to improve cache efficiency
https://github.com/facebook/redex - Android byte code optimizer
https://github.com/facebookincubator/SPARTA - Abstract analysis library behind ReDex
https://www.infoq.com/presentations/facebook-google-bpf-linux-kernel/ - eBPF - analysis built into the Linux Kernel
Not sure they fit 100% in a "static" or "dynamic" classification - but I'm leaning towards dynamic?
The text was updated successfully, but these errors were encountered: