Optimizing Java Bytecode Using the Soot Framework: Is It Feasible?
By Raja Vallée-Rai, Etienne M. Gagnon, Laurie J. Hendren, Patrick Lam, Patrice Pominville, Vijay Sundaresan. International Conference on Compiler Construction, 2000
391 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Software, Signal Processing
View Paper: https://www.semanticscholar.org/paper/22df3c0d055b7f65871068dfcd83d10f0a4fe2e4
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
- Patrick Drew McDaniel
- Laurie J. Hendren
- Ondřej Lhoták
- Xinming Ou
- Fengguo Wei
- Sankardas Roy
- Robby
- Nicolas Papernot
In Software
- Laurie J. Hendren
- Ondřej Lhoták
- Patrick Drew McDaniel
- Somesh Jha
- Martin C. Rinard
- Frank Tip
- Eric Bodden
- Damien Octeau
In Signal Processing
- Xinming Ou
- Fengguo Wei
- Sankardas Roy
- Robby
- Damien Octeau
- Laurie J. Hendren
- Ondřej Lhoták
- Yves Le Traon
Citations in the corpus
- Soot: a Java bytecode optimization framework (2010, methodology): “This method was mainly developed and added to the framework by Patrice Pominville and is described further in our overview paper [28].”
- Information Flow Analysis of Android Applications in DroidSafe (2015, methodology): “DroidSafe is developed on top of the Soot Java Analysis Framework [35].”
- A Study of Android Application Security (2011, neutral): “, Fernflower [1] or Soot [45].”
- abc: an extensible AspectJ compiler (2005, methodology): “As stated in the introduction, abc is based on the Polyglot extensible compiler framework [23] and the Soot bytecode analysis and transformation framework [26].”
- Scalable propagation-based call graph construction algorithms (2000, methodology): “The main problem for 0-CFA is that stack locations are unnamed in the Java virtual machine, so it seems necessary to rst do a program transformation that names all the locations in some fashion, as done in various recent work [ 41 , 38, 21].”
- Amandroid: A Precise and General Inter-component Data Flow Analysis Framework for Security Vetting of Android Apps (2014, methodology): “Existing off-the-shelf static analysis tools such as Soot [32] (used by FlowDroid [6, 17] and Epicc [25]) and Wala [16] (used by CHEX [23]) have not provided capability of calculating all objects’ points-to information in a both flow and context-sensitive way [4, 22].”
- Adding trace matching with free variables to AspectJ (2005, methodology): “abc uses Polyglot, an extensible Java compiler [25], as its front-end, and Soot, a Java bytecode analysis and transformation framework [29], as its backend.”
- Effective inter-component communication mapping in Android with Epicc: an essential step towards holistic security analysis (2013, methodology): “These classes are in Java bytecode format, since our analysis is built on top of Soot [34], an existing Java analysis framework.”
- Scaling Java Points-to Analysis Using SPARK (2003, methodology): “Spark is implemented as part of the Soot bytecode analysis, optimization, and annotation framework [27].”