[all-commits] [llvm/llvm-project] 62d4ad: [libunwind][AIX] Handle VAPI-based return addresse...

[Xing Xue via All-commits]

  Branch: refs/heads/release/23.x
  Home:   https://github.com/llvm/llvm-project
  Commit: 62d4ad9d04ce02a59edd12170418b93ea6334d7a
      https://github.com/llvm/llvm-project/commit/62d4ad9d04ce02a59edd12170418b93ea6334d7a
  Author: Xing Xue <xingxue at outlook.com>
  Date:   2026-07-23 (Thu, 23 Jul 2026)

  Changed paths:
    M libunwind/src/UnwindCursor.hpp

  Log Message:
  -----------
  [libunwind][AIX] Handle VAPI-based return addresses in stack unwinding for LLU (#209280)

In AIX's implementation of LLU (Live Library Update), the caller of a
Virtual API (VAPI) interface instead calls VAPI glue and the
implementation for a VAPI function is entered from the VAPI glue. If a
VAPI is not already active on the thread, the VAPI calls the
implementation of the VAPI function with the link register (LR) value
set to a return address in the VAPI glue. In this case, the LR (return
address) value on entry to the VAPI glue is saved in the VAPI control
block. This PR checks whether the return address in a stack frame falls
within the VAPI address range. If it does, the unwinder retrieves the LR
value from the VAPI control block and uses it as the return address
during stack unwinding. In addition, before transferring control to a
landing pad, this PR executes the VAPI return glue to clear the VAPI
control block if the VAPI glue was used.

---------

Co-authored-by: Hubert Tong <hubert.reinterpretcast at gmail.com>
(cherry picked from commit 8aa808457c6aeba25ec0e17139c3fcab59923c3c)



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications