7e486d5c2d
This adds the first strict element-wise named op to Linalg. The semantics here is to not allow auto-cast, broadcast semantics and to restrict the operations only to identical types. The remaining semantics must come in the form of surrounding operations on operands, to avoid ambiguity. Examples: ``` // Cast int-to-fp %0 = linalg.copy ins(%in: tensor<32x32xi32>) outs(%out: tensor<32x32xf32>) %1 = linalg.add ins(%arg, %0: tensor<32x32xf32>, tensor<32x32xf32>) outs(%0: tensor<32x32xf32>) // This can be lowered to %1 = linalg.generic {...} ins(%arg, %in: tensor<32x32xf32>, tensor<32x32xi32>) outs(%0: tensor<32x32xf32>) { ^bb0(%a: f32, %i: i32, %out: f32): %f = arith.uitofp %i : f32 %0 = arith.addf %a, %f : f32 linalg.yield %0 : f32 } // Broadcast %0 = linalg.broadcast ins(%in: tensor<32xf32>) init(%out: tensor<32x32xf32>) %1 = linalg.add ins(%arg, %0: tensor<32x32xf32>, tensor<32x32xf32>) outs(%0: tensor<32x32xf32>) // This can be lowered to #bcast_map = affine_map<(d0, d1) -> (d0)> %1 = linalg.generic {... #bcast_map] } ins(%arg, %in: tensor<32x32xf32>, tensor<32xf32>) outs(%0: tensor<32x32xf32>) { ^bb0(%a: f32, %b: f32, %out: f32): %0 = arith.addf %a, %b : f32 linalg.yield %0 : f32 } ``` Once this gets accepted, other arithmetic and maths operations will be added accordingly, with the same semantics. Differential Revision: https://reviews.llvm.org/D154500 |
||
---|---|---|
.github/workflows | ||
bolt | ||
clang | ||
clang-tools-extra | ||
cmake | ||
compiler-rt | ||
cross-project-tests | ||
flang | ||
libc | ||
libclc | ||
libcxx | ||
libcxxabi | ||
libunwind | ||
lld | ||
lldb | ||
llvm | ||
llvm-libgcc | ||
mlir | ||
openmp | ||
polly | ||
pstl | ||
runtimes | ||
third-party | ||
utils | ||
.arcconfig | ||
.arclint | ||
.clang-format | ||
.clang-tidy | ||
.git-blame-ignore-revs | ||
.gitignore | ||
.mailmap | ||
CONTRIBUTING.md | ||
LICENSE.TXT | ||
README.md | ||
SECURITY.md |
The LLVM Compiler Infrastructure
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.
Getting the Source Code and Building LLVM
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.
Getting in touch
Join the LLVM Discourse forums, Discord chat, or #llvm IRC channel on OFTC.
The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.