[DynInst_API:] [dyninst/dyninst] d5e2a6: Do not abort if symbolic expansion is not implemented


Date: Wed, 15 Feb 2023 11:15:03 -0800
From: Bolo -- Josef Burger <noreply@xxxxxxxxxx>
Subject: [DynInst_API:] [dyninst/dyninst] d5e2a6: Do not abort if symbolic expansion is not implemented
  Branch: refs/heads/bolo/johnmc_gfx908
  Home:   https://github.com/dyninst/dyninst
  Commit: d5e2a66c0536dfdb24b2569a385d40ea5e8a4454
      https://github.com/dyninst/dyninst/commit/d5e2a66c0536dfdb24b2569a385d40ea5e8a4454
  Author: Bolo <bolo@xxxxxxxxxxx>
  Date:   2023-02-15 (Wed, 15 Feb 2023)

  Changed paths:
    M dataflowAPI/src/SymEval.C

  Log Message:
  -----------
  Do not abort if symbolic expansion is not implemented
for an architecture.

Instead, return that symbolic expansion failed, and issue
an error message about that event.


  Commit: c7d1881c6e171e49fd42e0ee57dc0d022925f9ec
      https://github.com/dyninst/dyninst/commit/c7d1881c6e171e49fd42e0ee57dc0d022925f9ec
  Author: Bolo <bolo@xxxxxxxxxxx>
  Date:   2023-02-15 (Wed, 15 Feb 2023)

  Changed paths:
    M instructionAPI/src/Instruction.C

  Log Message:
  -----------
  Mark the AMDGPU setpc and swappc instructions as NOT
having follow through.

Previously these could be "fallen through" into none-code regions.

Just like a JMP or always-branch, there is no guarantee that the
next address is an instruction.


Compare: https://github.com/dyninst/dyninst/compare/d5e2a66c0536%5E...c7d1881c6e17
[← Prev in Thread] Current Thread [Next in Thread→]
  • [DynInst_API:] [dyninst/dyninst] d5e2a6: Do not abort if symbolic expansion is not implemented, Bolo -- Josef Burger <=