[all-commits] [llvm/llvm-project] 885509: [llvm-readobj] [ARMWinEH] Fix the interpretation o...

Martin Storsjö via All-commits all-commits at lists.llvm.org
Tue Dec 2 02:08:10 PST 2025


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 885509b1a2c08071c6b14eba84a2d80741cc9520
      https://github.com/llvm/llvm-project/commit/885509b1a2c08071c6b14eba84a2d80741cc9520
  Author: Martin Storsjö <martin at martin.st>
  Date:   2025-12-02 (Tue, 02 Dec 2025)

  Changed paths:
    M llvm/test/tools/llvm-readobj/COFF/arm64-packed-unwind.s
    M llvm/tools/llvm-readobj/ARMWinEHPrinter.cpp

  Log Message:
  -----------
  [llvm-readobj] [ARMWinEH] Fix the interpretation of packed unwind CR=01 RegI=1 (#169676)

Even though the table for how to expand packed unwind info at [1]
doesn't explicitly say this, this case is mentioned at [2] under the
case "Only x19 saved":

    sub    sp,sp,#16                // reg save area allocation*
    stp    x19,lr,[sp]              // save x19, lr
    sub    sp,sp,#(framesz-16)      // allocate the remaining local area

This was discussed and clarified at [3].

[1]
https://learn.microsoft.com/en-us/cpp/build/arm64-exception-handling?view=msvc-170#packed-unwind-data
[2]
https://learn.microsoft.com/en-us/cpp/build/arm64-exception-handling?view=msvc-170#arm64-stack-frame-layout
[3]
https://github.com/llvm/llvm-project/issues/169588#issuecomment-3581688753



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


More information about the All-commits mailing list