More fixes in jump table analysis:
authorXiaozhu Meng <xmeng@cs.wisc.edu>
Thu, 16 Apr 2015 03:32:49 +0000 (22:32 -0500)
committerXiaozhu Meng <xmeng@cs.wisc.edu>
Thu, 16 Apr 2015 03:32:49 +0000 (22:32 -0500)
commitad1087329046e41bc7d89ab3d009cd5088636765
treee58fd46cd990d5bc9076580616f1fbb537b019ff
parent0645a64ce753391a4bf0a8ebe31c63e9c7dec86b
More fixes in jump table analysis:
1. Do not add control flow paths that slicer has not visited, otherwise there may be some instructions that affects target calculations
2. Need to track aliases across several variables
dataflowAPI/h/slicing.h
dataflowAPI/src/slicing.C
parseAPI/src/BoundFactCalculator.C
parseAPI/src/BoundFactData.C
parseAPI/src/IndirectAnalyzer.C
parseAPI/src/JumpTablePred.C
parseAPI/src/JumpTablePred.h