aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
diff options
context:
space:
mode:
authorMatheus Izvekov <mizvekov@gmail.com>2023-11-17 11:39:20 +0100
committerGitHub <noreply@github.com>2023-11-17 11:39:20 +0100
commita67b85ef63c7ec29c2076294e3f7c7f923144a53 (patch)
tree73b9a65ef74262d03fab6ec0c0b8c8720bc11f44 /llvm/lib/Bitcode/Writer/BitcodeWriter.cpp
parent7aaa86b28ddc3deded6e357b27f2bbebb97a3864 (diff)
downloadllvm-a67b85ef63c7ec29c2076294e3f7c7f923144a53.zip
llvm-a67b85ef63c7ec29c2076294e3f7c7f923144a53.tar.gz
llvm-a67b85ef63c7ec29c2076294e3f7c7f923144a53.tar.bz2
Add llvm-dlltool to the toolchain list (#72563)
This adds dlltool to the list of tools which don't get excluded from installation when LLVM_INSTALL_TOOLCHAIN_ONLY is set. The most important effect here is that this tool will now be included in the official Windows release. While llvm-lib reuses the dlltool machinary internally and has many of the same capabilities, it does not expose the functionality controller by the '-k' flag, which is currently the only way to create import libraries for i386 with stdcall symbols from a module definition alone. We avoid changing llvm-lib tool, since it is designed to emulate LIB.EXE from MSVC toolchain, and as this functionality is not supported there, we would have had to introduce an LLVM extension flag in order to support it. See https://reviews.llvm.org/D36548 for reference on rationale for dlltool '-k' flag.
Diffstat (limited to 'llvm/lib/Bitcode/Writer/BitcodeWriter.cpp')
0 files changed, 0 insertions, 0 deletions