[mlir][xegpu] Add vector layout conflict handling in XeGPU layout propagation pass. (#182402) This PR adds support for layout conflict handling for vector operands. A conflict for a vector operand occurs when a value consumed at a given operand is not in the expected layout in the context of the consumer (for example `vector.multi_reduction` op's source require a specific layout inferred from its current result layout). To resolve this conflict, we insert an `xegpu.convert_layout` right after the producer (essentially duplicating the producer with expected layout) and use the new value in the consumer.
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.