[all-commits] [llvm/llvm-project] 96f093: [dsymutil] Add option to copy swiftmodules built f...

[Roy Shi via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 96f093770d21b8bbe05a6b8ff744ce9fdd6e4c50
      https://github.com/llvm/llvm-project/commit/96f093770d21b8bbe05a6b8ff744ce9fdd6e4c50
  Author: Roy Shi <royitaqi at users.noreply.github.com>
  Date:   2025-11-03 (Mon, 03 Nov 2025)

  Changed paths:
    M llvm/docs/CommandGuide/dsymutil.rst
    A llvm/test/tools/dsymutil/ARM/swiftmodule-include-from-interface.test
    M llvm/test/tools/dsymutil/cmdline.test
    M llvm/tools/dsymutil/DwarfLinkerForBinary.cpp
    M llvm/tools/dsymutil/LinkUtils.h
    M llvm/tools/dsymutil/Options.td
    M llvm/tools/dsymutil/dsymutil.cpp

  Log Message:
  -----------
  [dsymutil] Add option to copy swiftmodules built from interface (#165293)

The default behavior is to _not_ copy such swiftmodules into the dSYM,
as perviously implemented in 96f95c9d89d8a1784d3865fa941fb1c510f4e2d7.
This patch adds the option to override the behavior, so that such
swiftmodules can be copied into the dSYM.

This is useful when the dSYM will be used on a machine which has a
different Xcode/SDK than where the swiftmodules were built. Without
this, when LLDB is asked to "p/po" a Swift variable, the underlying
Swift compiler code would rebuild the dependent `.swiftmodule` files of
the Swift stdlibs, which takes ~1 minute in some cases.

See PR for tests.



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