[DTLTO] Fix handling of multi-module bitcode inputs (#174624) This change fixes two issues when processing multi-module bitcode files in DTLTO: 1. The DTLTO archive handling code incorrectly uses getSingleBitcodeModule(), which asserts when the bitcode file contains more than one module. 2. The temporary file containing the contents of an input archive member was not emitted for multi-module bitcode files. This was due to incorrect logic for recording whether a bitcode input contains any ThinLTO modules. In a typical multi-module bitcode file, the first module is a ThinLTO module while a subsequent auxiliary module is non-ThinLTO. When modules are processed in order, the auxiliary module causes the entire bitcode file to be classified as non-ThinLTO, and the archive-member emission logic then incorrectly skips it. In addition, this patch adds a test that verifies that multi-module bitcode files can be successfully linked with DTLTO. The test reproduces both issues as they existed prior to this change. SIE Tracker: TOOLCHAIN-21008
Welcome to the LLVM project!
This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.
The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.
C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.
Other components include: the libc++ C++ standard library, the LLD linker, and more.
Consult the Getting Started with LLVM page for information on building and running LLVM.
For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.
Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.