|
From: <fra...@us...> - 2009-04-18 03:51:00
|
Revision: 1418
http://javapathfinder.svn.sourceforge.net/javapathfinder/?rev=1418&view=rev
Author: frankrimlinger
Date: 2009-04-18 03:50:58 +0000 (Sat, 18 Apr 2009)
Log Message:
-----------
Created extension of JPF, called JPF_MIRROR, whose main routine creates the vm but does not fire up a thread and run. Now comes an interesting issue. Mango needs to do an analysis of the "entire" code body in order to convert loops to recursive functions. But jpf pulls in classes on-the-fly, starting out with just enough grist for the mill. This is certainly more elegant, but jpf doesn't necessarily "care" about complete coverage of all paths. It seems quite likely there is an option for such a preference, and I will investigate. In any case, the idea is to give jpf the method to be analyzed as the "main" routine and let it run through though all edges of the forward control flow graph at least once. This will cause all the invovled classes to get pulled in. Once I have all the relevant class models then mango can do its thing, creating "advice" for future jpf runs.
Modified Paths:
--------------
branches/mango/MangoJPF/.classpath
branches/mango/MangoJPF/.project
branches/mango/MangoJPF/Mango/src/mango/control/msg/StartRequestMsg.java
branches/mango/MangoJPF/Mango/src/mango/worker/Mango.java
branches/mango/MangoJPF/Mango/src/mango/worker/javaModel/classParser/ClassParsingAlg.java
branches/mango/MangoJPF/Mango/src/mango/workstation/Workstation.java
Added Paths:
-----------
branches/mango/MangoJPF/javapathfinder-trunk-MIRROR/
branches/mango/MangoJPF/javapathfinder-trunk-MIRROR/gov/
branches/mango/MangoJPF/javapathfinder-trunk-MIRROR/gov/nasa/
branches/mango/MangoJPF/javapathfinder-trunk-MIRROR/gov/nasa/jpf/
branches/mango/MangoJPF/javapathfinder-trunk-MIRROR/gov/nasa/jpf/JPF_MIRROR.java
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|