[all-commits] [llvm/llvm-project] 1a0f28: [NFC] Extract DWARFCFIProgram into separate files ...

[Sterling-Augustine via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 1a0f284dea009889af930c4a6db7b0a92c941c8a
      https://github.com/llvm/llvm-project/commit/1a0f284dea009889af930c4a6db7b0a92c941c8a
  Author: Sterling-Augustine <56981066+Sterling-Augustine at users.noreply.github.com>
  Date:   2025-06-02 (Mon, 02 Jun 2025)

  Changed paths:
    A llvm/include/llvm/DebugInfo/DWARF/DWARFCFIProgram.h
    M llvm/include/llvm/DebugInfo/DWARF/DWARFDebugFrame.h
    M llvm/lib/DebugInfo/DWARF/CMakeLists.txt
    A llvm/lib/DebugInfo/DWARF/DWARFCFIProgram.cpp
    M llvm/lib/DebugInfo/DWARF/DWARFDebugFrame.cpp

  Log Message:
  -----------
  [NFC] Extract DWARFCFIProgram into separate files (#139326)

CFIPrograms' most common uses are within debug frames, but it is not
their only use. For example, some assembly writers encode them by hand
into .cfi_escape directives. This PR extracts code for them into its own
files, setting them up to be evaluated from outside debug frames
themselves.

One in a series of NFC DebugInfo/DWARF refactoring changes to layer it
more cleanly, so that binary CFI parsing can be used from low-level
code, (such as byte strings created via .cfi_escape) without circular
dependencies. The final goal is to make a more limited dwarf library
usable from lower-level code.



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