[Soot-list] Seeking proposals for Google Summer Of Code projects

Eric Bodden eric.bodden at ec-spride.de
Sun Feb 17 04:12:34 EST 2013


> A long time ago, I tried to dump Jimple to disk and re-parse it. It
> didn't save that much time for me. It shouldn't be hard to give that a
> try and see if it's actually faster; caching it on the web is only going
> to be faster if it's faster to read it from disk.

I agree.

The other thing we realized is the following: When using a standard
analysis mechanism such as our IDE solver then it should be possible
to cache instead of the full Jimple just summary information about
this Jimple code with respect to a particular (IDE based) data-flow
analysis. If, for an API, such summaries are fully available then one
would not even load the Jimple for the library any more at all. This
would basically be a refinement of this work:

Atanas Rountev, Mariana Sharp, and Guoqing Xu. 2008. IDE dataflow
analysis in the presence of large object-oriented libraries. In
Proceedings of the Joint European Conferences on Theory and Practice
of Software 17th international conference on Compiler construction
(CC'08/ETAPS'08), Laurie Hendren (Ed.). Springer-Verlag, Berlin,
Heidelberg, 53-68.

I think that would be a nice project and in fact it's one of the
topics I proposed.

Eric


More information about the Soot-list mailing list