[DynInst_API:] [dyninst/dyninst] c6144a: For jump table analysis, control flow edges can be...

[Xiaozhu Meng <noreply@xxxxxxxxxx>]

  Branch: refs/heads/pp_springboard
  Home:   https://github.com/dyninst/dyninst
  Commit: c6144ad78965c02708e67a8d65dabb5ba9c607b6
      https://github.com/dyninst/dyninst/commit/c6144ad78965c02708e67a8d65dabb5ba9c607b6
  Author: Xiaozhu Meng <xmeng@xxxxxxxxxxx>
  Date:   2019-04-23 (Tue, 23 Apr 2019)

  Changed paths:
    M dataflowAPI/src/slicing.C

  Log Message:
  -----------
  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.