For jump table analysis, control flow edges can be created in different orders,
authorXiaozhu Meng <xmeng@cs.wisc.edu>
Tue, 23 Apr 2019 14:02:39 +0000 (09:02 -0500)
committerXiaozhu Meng <xmeng@cs.wisc.edu>
Tue, 23 Apr 2019 14:02:39 +0000 (09:02 -0500)
commitc6144ad78965c02708e67a8d65dabb5ba9c607b6
treeaa7f9aecf66b67a81e2941f0e3d3ad940891c2a7
parent57b8030b30c9e6b5ecc5fa0a705316a9a683e38b
For jump table analysis, control flow edges can be created in different orders,
which lead to non-deterministic slicing and non-determinisitc jump table analysis.

Therefore, we need to sort source edges in slicing based on the edge's source block
address and edge type to ensure deterministic slicing.
dataflowAPI/src/slicing.C