| commit | 43c85afce9c25141de79da6731b1d5f8bb2491b1 | [log] [tgz] |
|---|---|---|
| author | Peter Collingbourne <peter@pcc.me.uk> | Thu Aug 28 19:13:53 2025 -0700 |
| committer | GitHub <noreply@github.com> | Thu Aug 28 19:13:53 2025 -0700 |
| tree | 4c97fe1780d00df5905543f239a68cf1f327558b | |
| parent | 2a062d693693f92d80656cb2b334b7dc8e08121f [diff] |
ThinLTOBitcodeWriter: Split modules with __cfi_check and no type metadata. Eli Friedman found a case that was not handled correctly by #154833 where we failed to split the module if it contained a __cfi_check function but no type metadata. Handle this case correctly by checking for __cfi_check when deciding whether to split. Reviewers: teresajohnson, efriedma-quic Reviewed By: efriedma-quic Pull Request: https://github.com/llvm/llvm-project/pull/155930
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.