[all-commits] [llvm/llvm-project] 0be7ac: [dsymutil] Thread the VFS through dsymutil (NFC)

[Jonas Devlieghere via All-commits]

  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: 0be7acab1573accb2943673df5f1fc9331e196d0
      https://github.com/llvm/llvm-project/commit/0be7acab1573accb2943673df5f1fc9331e196d0
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2020-05-04 (Mon, 04 May 2020)

  Changed paths:
    M llvm/tools/dsymutil/BinaryHolder.cpp
    M llvm/tools/dsymutil/BinaryHolder.h
    M llvm/tools/dsymutil/DebugMap.cpp
    M llvm/tools/dsymutil/DwarfLinkerForBinary.cpp
    M llvm/tools/dsymutil/LinkUtils.h
    M llvm/tools/dsymutil/MachODebugMapParser.cpp
    M llvm/tools/dsymutil/MachOUtils.cpp
    M llvm/tools/dsymutil/MachOUtils.h
    M llvm/tools/dsymutil/dsymutil.cpp
    M llvm/tools/dsymutil/dsymutil.h

  Log Message:
  -----------
  [dsymutil] Thread the VFS through dsymutil (NFC)

This patch threads the virtual file system through dsymutil.

Currently there is no good way to find out exactly what files are
necessary in order to reproduce a dsymutil link, at least not without
knowledge of how dsymutil's internals.  My motivation for this change is
to add lightweight "reproducers" that automatically gather the input
object files through the FileCollectorFileSystem. The files together
with the YAML mapping will allow us to transparently reproduce a
dsymutil link, even without having to mess with the OSO path prefix.

Differential revision: https://reviews.llvm.org/D79376