[MLIR][LLVM] Fix crash in LLVMFunctionType::clone when erasing void function results (#185093) LLVMFunctionType::clone(inputs, results) was asserting that results.size() == 1, which caused a crash (later changed to return null/failure) when erasing results from a void llvm.func via FunctionOpInterface::eraseResults. For LLVM function types, an empty results range maps to void return: the FunctionOpInterface represents void llvm.func with 0 results, while the underlying LLVMFunctionType stores an explicit LLVMVoidType. When erasing all results (or no-op erasing 0 results from a void function), the interface passes an empty TypeRange to clone(), which should produce a void function type. Fix by accepting an empty results range in LLVMFunctionType::clone() and mapping it to LLVMVoidType. More than one result remains invalid. Fixes #128322 Assisted-by: Claude Code
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.