| commit | 045b82736702799f7f56da2f98a3fa1f2fae8d46 | [log] [tgz] |
|---|---|---|
| author | Daniel Man <man.daniel.dev@gmail.com> | Fri Jun 27 00:41:22 2025 -0700 |
| committer | GitHub <noreply@github.com> | Fri Jun 27 16:41:22 2025 +0900 |
| tree | 559e54e2c1628a8a0aec7a985959bcdacc065439 | |
| parent | 8a839ea79123175c940a64beea6abd29b8b302fb [diff] |
[GlobalISel] Use-Vector-Truncate Opt Needs Elt Type Check (#146003) In the pre-legalizer combiner, there exists a bug with UseVectorTruncate match-apply optimization. When the destinations' types do not match the vector element type of the G_UNMERGE_VALUES instruction, the resulting collapsed truncate does not preserve original functional behavior. This commit introduces a simple type check to ensure that the destination types match the vector element type.
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.