[Inline] Allow inlining with null_pointer_is_valid mismatch (#190510) If the callee has null_pointer_is_valid but the caller does not, we should still inline and add null_pointer_is_valid to the caller (which is handled by an already existing inline adjustment rule). This does mean that optimizations in the caller may be reduced by unnecessarily preserving null checks, but that's still better than not inlining at all. In particular, this check causes issues with LTO in the Linux kernel, as the C portions are compiled with null_pointer_is_valid, but the Rust portions are not. The test is modified to show that the previous alwaysinline behavior now always holds.
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.