[Soot-list] Speeding up soot in whole-program mode ?
chris.pickett at mail.mcgill.ca
Sun Oct 2 17:40:43 EDT 2005
Guillaume Salagnac wrote:
> But anyway, it seems that loading the jimple is not faster than parsing
> bytecode, so I gave up this approach. That's why there is no emergency
> in fixing this bug.
> I was hoping that parsing the jimple would speed up soot's execution,
> because some phases are not useful anymore : the jimple locals are
> already there, already typed, etc. But I was wrong, as I discovered
> Is there such a way to reduce the execution time when working whith
> .jimple source, for example by ommiting some soot phases, like jimple
> typing, and so on ? Obviously, if the jimple is already built, it is not
> useful to do it a second time...
Hmmm... why don't you look into object serialization? Maybe you could
use a dummy non-Soot application as a quick proof-of-concept.
More information about the Soot-list