[all-commits] [llvm/llvm-project] c9c687: [NFC] Split portions of DWARFDataExtractor into ne...

Sterling-Augustine via All-commits all-commits at lists.llvm.org
Fri Jun 6 09:27:13 PDT 2025


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

  Changed paths:
    M llvm/include/llvm/DebugInfo/DWARF/DWARFDataExtractor.h
    A llvm/include/llvm/DebugInfo/DWARF/DWARFDataExtractorSimple.h
    M llvm/lib/DebugInfo/DWARF/CMakeLists.txt
    R llvm/lib/DebugInfo/DWARF/DWARFDataExtractor.cpp

  Log Message:
  -----------
  [NFC] Split portions of DWARFDataExtractor into new class (#140096)

Currently, DWARFDataExtractor can extract data without performing
relocations, (eg, by checking if the section pointer is null) but is
coded such that it still depends on all the relocation machinery, like
DWARFSections and similar. All at build time.

Extract most functionality into a new class, DWARFDataExtractorBase, and 
have DWARFDataExtractor add the relocation dependent pieces via CRTP.  
Add a new class, DWARFDataExtractorSimple, which does no relocation at 
all. This will allow moving DWARFDataExtractorSimple into a new lower-level, 
lighter-weight library with fewer external build-time dependencies.

This is another in a series of refactoring changes to create a new
better-layered, low-level Dwarf library that can be called from
lower-level code without circular dependencies.



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