Find a file
Benoit Jacob 0aea49a730 [mlir][Vector] Patterns flattening vector transfers to 1D
This is the first part of https://reviews.llvm.org/D114993 which has been
split into small independent commits.

This is needed at the moment to get good codegen from 2d vector.transfer
ops that aim to compile to SIMD load/store instructions but that can
only do so if the whole 2d transfer shape is handled in one piece, in
particular taking advantage of the memref being contiguous rowmajor.

For instance, if the target architecture has 128bit SIMD then we would
expect that contiguous row-major transfers of <4x4xi8> map to one SIMD
load/store instruction each.

The current generic lowering of multi-dimensional vector.transfer ops
can't achieve that because it peels dimensions one by one, so a transfer
of <4x4xi8> becomes 4 transfers of <4xi8>.

The new patterns here are only enabled for now by
 -test-vector-transfer-flatten-patterns.

Reviewed By: nicolasvasilache
2021-12-13 21:49:04 +00:00
.github Use "new issue" label for tagging new issues 2021-12-12 13:38:26 -08:00
clang Revert "[NFC][Clang][OpenMP] Use switch-case statement to process clauses of atomic directive" 2021-12-13 16:31:04 -05:00
clang-tools-extra [clangd][Dex] Fix crashes when building trigrams for empty identifier 2021-12-13 15:58:33 +01:00
cmake/Modules [libunwind] Try to add --unwindlib=none while configuring and building libunwind 2021-11-05 10:10:19 +02:00
compiler-rt [NFC][asan] XFAIL a test on THUMB 2021-12-13 12:07:13 -08:00
cross-project-tests [dexter] Fix source-root-dir unittests on Windows 2021-12-08 15:43:02 +00:00
flang [Flang][Unit Test] Move the declaration of kindMap to the class 2021-12-13 16:12:01 +00:00
libc [libc][NFC] Remove dependecies on entrypoints from loader tests. 2021-12-13 19:29:29 +00:00
libclc Quote some more destination paths with variables 2021-12-13 17:29:08 +00:00
libcxx [libc++] Change workaround for init_priority((100)) outside of system headers 2021-12-13 14:37:54 -05:00
libcxxabi [libc++abi][NFC] Fix comment 2021-12-13 10:29:29 -05:00
libunwind [libc++][release] Do not force building the runtimes with -fPIC 2021-12-08 11:34:35 -05:00
lld [ELF] Split scanRelocations into scanRelocations/postScanRelocations 2021-12-13 09:56:52 -08:00
lldb Add support for a "load binary" LC_NOTE in mach-o corefiles 2021-12-13 13:21:56 -08:00
llvm Revert "[LTO] Add a function LTOCodeGenerator::getMergedModule" 2021-12-13 16:31:22 -05:00
mlir [mlir][Vector] Patterns flattening vector transfers to 1D 2021-12-13 21:49:04 +00:00
openmp Quote some more destination paths with variables 2021-12-13 17:29:08 +00:00
polly [Polly][Isl] Fix -Wsign-compare after D113101 2021-11-11 00:17:52 -08:00
pstl [pstl] Fix incorrect usage of std::invoke_result 2021-11-26 17:29:08 +03:00
runtimes Reapply #2 of [runtimes] Fix building initial libunwind+libcxxabi+libcxx with compiler implied -lunwind 2021-12-09 21:38:14 +02:00
third-party/benchmark [benchmark] Reapply fix for -Wcovered-switch-default warning 2021-12-09 21:39:29 +02:00
utils [libc] Bazel overlay for libc 2021-12-13 19:14:22 +00:00
.arcconfig
.arclint
.clang-format
.clang-tidy
.git-blame-ignore-revs
.gitignore
.mailmap
CONTRIBUTING.md
README.md
SECURITY.md

The LLVM Compiler Infrastructure

This directory and its sub-directories contain source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.

The README briefly describes how to get started with building LLVM. For more information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.

Getting Started with the LLVM System

Taken from https://llvm.org/docs/GettingStarted.html.

Overview

Welcome to the LLVM project!

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. It also contains basic regression tests.

C-like languages use the Clang front end. 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

The LLVM Getting Started documentation may be out of date. The Clang Getting Started page might have more accurate information.

This is an example work-flow and configuration to get and build the LLVM source:

  1. Checkout LLVM (including related sub-projects like Clang):

    • git clone https://github.com/llvm/llvm-project.git

    • Or, on windows, git clone --config core.autocrlf=false https://github.com/llvm/llvm-project.git

  2. Configure and build LLVM and Clang:

    • cd llvm-project

    • cmake -S llvm -B build -G <generator> [options]

      Some common build system generators are:

      • Ninja --- for generating Ninja build files. Most llvm developers use Ninja.
      • Unix Makefiles --- for generating make-compatible parallel makefiles.
      • Visual Studio --- for generating Visual Studio projects and solutions.
      • Xcode --- for generating Xcode projects.

      Some common options:

      • -DLLVM_ENABLE_PROJECTS='...' --- semicolon-separated list of the LLVM sub-projects you'd like to additionally build. Can include any of: clang, clang-tools-extra, compiler-rt,cross-project-tests, flang, libc, libclc, libcxx, libcxxabi, libunwind, lld, lldb, mlir, openmp, polly, or pstl.

        For example, to build LLVM, Clang, libcxx, and libcxxabi, use -DLLVM_ENABLE_PROJECTS="clang;libcxx;libcxxabi".

      • -DCMAKE_INSTALL_PREFIX=directory --- Specify for directory the full path name of where you want the LLVM tools and libraries to be installed (default /usr/local).

      • -DCMAKE_BUILD_TYPE=type --- Valid options for type are Debug, Release, RelWithDebInfo, and MinSizeRel. Default is Debug.

      • -DLLVM_ENABLE_ASSERTIONS=On --- Compile with assertion checks enabled (default is Yes for Debug builds, No for all other build types).

    • cmake --build build [-- [options] <target>] or your build system specified above directly.

      • The default target (i.e. ninja or make) will build all of LLVM.

      • The check-all target (i.e. ninja check-all) will run the regression tests to ensure everything is in working order.

      • CMake will generate targets for each tool and library, and most LLVM sub-projects generate their own check-<project> target.

      • Running a serial build will be slow. To improve speed, try running a parallel build. That's done by default in Ninja; for make, use the option -j NNN, where NNN is the number of parallel jobs, e.g. the number of CPUs you have.

    • For more information see CMake

Consult the Getting Started with LLVM page for detailed information on configuring and compiling LLVM. You can visit Directory Layout to learn about the layout of the source code tree.