[all-commits] [llvm/llvm-project] 81d3c1: [DWARFLinker] Support parseable Swift interfaces i...

Jonas Devlieghere via All-commits all-commits at lists.llvm.org
Tue May 5 10:39:10 PDT 2026


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 81d3c19137011a8f46495c8a3a24cf8a8c0a20df
      https://github.com/llvm/llvm-project/commit/81d3c19137011a8f46495c8a3a24cf8a8c0a20df
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2026-05-05 (Tue, 05 May 2026)

  Changed paths:
    M llvm/lib/DWARFLinker/Parallel/DWARFLinkerCompileUnit.cpp
    M llvm/lib/DWARFLinker/Parallel/DWARFLinkerCompileUnit.h
    M llvm/lib/DWARFLinker/Parallel/DWARFLinkerImpl.cpp
    M llvm/test/tools/dsymutil/X86/swift-interface.test

  Log Message:
  -----------
  [DWARFLinker] Support parseable Swift interfaces in the parallel linker (#195475)

CompileUnit::Language was filtered through isODRLanguage at construction,
so non-ODR languages landed as std::nullopt and analyzeImportedModule's
Swift branch was never reached under --linker parallel. Store the raw
DW_AT_language and apply isODRLanguage only where ODR is actually
decided.

Reaching that branch then exposes a shared-map write from
parallelForEach workers. A mutex would make it safe but not
deterministic: conflict warnings and last-writer-wins contents would
depend on thread scheduling and diverge from the classic linker. Stage
entries per-CU and merge them serially in input order after analysis, so
results match classic regardless of schedule.

Because the diagnostics are emitted after unloading the input, we do
lose the originating DW_TAG_module. The warning still names the module
and both conflicting paths, which carries the load-bearing information.



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