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

Eric Bodden eric.bodden at ec-spride.de
Fri Feb 22 03:04:40 EST 2013


Ho Richard.

> If I were right, Andromeda resolves aliases first and performs IDE analysis.
> Basically, Of course, we can feed a non-distributed problem to a distributed
> solver, the only problem is how precise it is. Therefore, a non-distributive
> summary database is useful that everybody who owns big servers can shares
> her precise semi-product to other Soot users. It's no doubt that everybody
> wants precise result but the only problem is the high price to pay. Sharing
> can alleviate the pain significantly. If we can build such an open
> infrastructure, I think that's very attractive to all Java researchers.

Now I see what you mean. That's an interesting idea! I will think
about how something like that could be accomplished.


> Personally, I wrote a points-to analysis persistence tool for Soot. It's
> also a pain to re-run Spark or other points-to engines again and again, so I
> make a persistent and compact disk index for the points-to result.
> Therefore, we only run Spark once and query it anytime and anywhere. This
> saves a lot of time for recomputing and a lot of memory for querying because
> of the index is quite small. This is not fully integrated with Soot now, I
> will submit as a patch in future. But of course, I believe the summary
> database is more useful than my tool.

That would be a great contribution and most welcome!

Cheers,
Eric


More information about the Soot-list mailing list