DASCA
/
WALA
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

switched to 0-CFA call graphs 

git-svn-id: https://wala.svn.sourceforge.net/svnroot/wala/trunk@2668 f5eafffb-2e1d-0410-98e4-8ec43c5233c4
This commit is contained in:
msridhar1 2008-03-04 17:32:26 +00:00
parent b4439c7a76
commit bb2d20cba4
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
com.ibm.wala.core.tests/src/com/ibm/wala/core/tests/demandpa/AbstractPtrTest.java
View File

@ -198,12 +198,9 @@ public abstract class AbstractPtrTest extends TestCase {
AnalysisOptions options = CallGraphTestUtil.makeAnalysisOptions(scope, entrypoints);
final AnalysisCache analysisCache = new AnalysisCache();
// in general, RTA call graphs should not be used due to unsound handling
// of clone() for pointer analysis, but some tests rely on RTA CG precision
// so we use it here
CallGraphBuilder cgBuilder = Util.makeRTABuilder(options, analysisCache, cha, scope);
CallGraphBuilder cgBuilder = Util.makeZeroCFABuilder(options, analysisCache, cha, scope);
final CallGraph cg = cgBuilder.makeCallGraph(options, null);
// System.err.println(cg.toString());
// System.err.println(cg.toString());
MemoryAccessMap fam = new SimpleMemoryAccessMap(cg, false);
SSAPropagationCallGraphBuilder builder = Util.makeVanillaZeroOneCFABuilder(options, analysisCache, cha, scope);