[all-commits] [llvm/llvm-project] 56085f: [DebugInfo] Add DWARFUnit::clearDWO()

[Rafael Auler via All-commits]

  Branch: refs/heads/users/rafaelauler/dwarfunit_getdwo
  Home:   https://github.com/llvm/llvm-project
  Commit: 56085f9db55022a7eace22a3c1ebf7e1f877f39d
      https://github.com/llvm/llvm-project/commit/56085f9db55022a7eace22a3c1ebf7e1f877f39d
  Author: Rafael Auler <rafaelauler at fb.com>
  Date:   2026-08-07 (Fri, 07 Aug 2026)

  Changed paths:
    M llvm/include/llvm/DebugInfo/DWARF/DWARFUnit.h

  Log Message:
  -----------
  [DebugInfo] Add DWARFUnit::clearDWO()

Add DWARFUnit::clearDWO() so a skeleton unit can drop the DWO context
it owns without being destroyed itself. Also add DWARFUnit::hasDWO()
to answer if that skeleton CU is currently caching a DWO context, so
users can easily look it up.

For example, BOLT opened a DWARFContext for every .dwo during
readDebugInfo and kept them all alive until teardown. On large
split-DWARF targets that is tens of GiB held
resident. clearDWO()/hasDWO() expose to users DWARFUnit's caching
capacity, allowing them to spontaneously drop the cache/look it
up/re-load it for memory management.



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