| commit | 2a5ac19605ae49d6628ac3af55d6b528cb13ed2e | [log] [tgz] |
|---|---|---|
| author | Luke Lau <luke@igalia.com> | Wed Jul 30 13:14:28 2025 +0800 |
| committer | Luke Lau <luke@igalia.com> | Wed Jul 30 13:29:47 2025 +0800 |
| tree | a88f1be3bb85acf7ea143a76b8ad10dc9c0e5b9a | |
| parent | f527b319e377202e44b14b6875584a558a628803 [diff] |
Revert "[RISCV] Cost bf16/f16 vector non-unit memory accesses as legal without zvfhmin/zvfbfmin (#150882)" This reverts commit fe4f6c1a58ab4f00a88a97af01000b6783b573ee, but leaves the tests that were added. The original commit mistakenly assumed that if regular bf16/f16 loads and stores could be lowered without zvfbfmin/zvfhmin, then so too could masked loads/stores and gathers/scatters. However SelectionDAG can't actually type-legalize masked.load/stores since it needs to be done in ScalarizeMaskedMemIntrinPass. This was causing crashes on IREE because we now returned true for isLegalMaskedLoadStore. The original intent of this was to remove a discrepancy in the loop vectorizer tests whenever predication was enabled, but this has gone away after 92d09245d61dce80d3e68a27cc34d5fc6f062c93. So I don't think we need to reapply this patch.
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.