[DynInst_API:] [dyninst/dyninst] 73c3bb: A memory access to a known address should be consi...


Date: Fri, 24 Feb 2017 09:19:39 -0800
From: Bill Williams <wwilliam47@xxxxxxxxx>
Subject: [DynInst_API:] [dyninst/dyninst] 73c3bb: A memory access to a known address should be consi...
  Branch: refs/heads/v9.3.x
  Home:   https://github.com/dyninst/dyninst
  Commit: 73c3bb0999f0e5afe44bc70d0fbb16ea9d42b3dc
      https://github.com/dyninst/dyninst/commit/73c3bb0999f0e5afe44bc70d0fbb16ea9d42b3dc
  Author: Xiaozhu Meng <xmeng@xxxxxxxxxxx>
  Date:   2017-02-23 (Thu, 23 Feb 2017)

  Changed paths:
    M parseAPI/src/BoundFactData.C
    M parseAPI/src/IndirectASTVisitor.C

  Log Message:
  -----------
  A memory access to a known address should be considered as a variable, rather than a table read.
So, the jump table analysis should not try to read the content of the variable, but try to determine whether the variable is bounded


  Commit: 54f1b1e16064332983f0a35db58bd5a0234925ad
      https://github.com/dyninst/dyninst/commit/54f1b1e16064332983f0a35db58bd5a0234925ad
  Author: Bill Williams <wwilliam47@xxxxxxxxx>
  Date:   2017-02-24 (Fri, 24 Feb 2017)

  Changed paths:
    M parseAPI/src/BoundFactData.C
    M parseAPI/src/IndirectASTVisitor.C

  Log Message:
  -----------
  Merge pull request #338 from dyninst/meng/lulesh-fix

Fix jump table analysis for lulesh


Compare: https://github.com/dyninst/dyninst/compare/d3fa4d831dd1...54f1b1e16064
[← Prev in Thread] Current Thread [Next in Thread→]