Go to file

Mikhail Maltsev dd4d093762 [ARM] Add initial support for Custom Datapath Extension (CDE) Summary: This patch adds assembly-level support for a new Arm M-profile architecture extension, Custom Datapath Extension (CDE). A brief description of the extension is available at https://developer.arm.com/architectures/instruction-sets/custom-instructions The latest specification for CDE is currently a beta release and is available at https://static.docs.arm.com/ddi0607/aa/DDI0607A_a_armv8m_arm_supplement_cde.pdf CDE allows chip vendors to add custom CPU instructions. The CDE instructions re-use the same encoding space as existing coprocessor instructions (such as MRC, MCR, CDP etc.). Each coprocessor in range cp0-cp7 can be configured as either general purpose (GCP) or custom datapath (CDEv1). This configuration is defined by the CPU vendor and is provided to LLVM using 8 subtarget features: cdecp0 ... cdecp7. The semantics of CDE instructions are implementation-defined, but the instructions are guaranteed to be pure (that is, they are stateless, they do not access memory or any registers except their explicit inputs/outputs). CDE requires the CPU to support at least Armv8.0-M mainline architecture. CDE includes 3 sets of instructions: * Instructions that operate on general purpose registers and NZCV flags * Instructions that operate on the S or D register file (require either FP or MVE extension) * Instructions that operate on the Q register file, require MVE The user-facing names that can be specified on the command line are the same as the 8 subtarget feature names. For example: $ clang -target arm-none-none-eabi -march=armv8m.main+cdecp0+cdecp3 tells the compiler that the coprocessors 0 and 3 are configured as CDEv1 and the remaining coprocessors are configured as GCP (which is the default). Reviewers: simon_tatham, ostannard, dmgreen, eli.friedman Reviewed By: simon_tatham Subscribers: kristof.beyls, hiraditya, cfe-commits, llvm-commits Tags: #clang, #llvm Differential Revision: https://reviews.llvm.org/D74044		2020-02-17 15:39:16 +00:00
clang	[ARM] Add initial support for Custom Datapath Extension (CDE)	2020-02-17 15:39:16 +00:00
clang-tools-extra	Strength reduce vectors into arrays. NFCI.	2020-02-17 15:37:35 +01:00
compiler-rt	[compiler-rt] Make various Apple lit substitutions work correctly for other Apple platforms.	2020-02-14 13:53:54 -08:00
debuginfo-tests	[debuginfo-tests][Dexter] Fix some Windows-unfriendly Dexter behaviours	2020-02-13 14:24:33 +00:00
libc	[libc] Add Convenience syscall Template Function	2020-02-13 14:39:16 -05:00
libclc	libclc/r600: Use target specific builtins to implement rsqrt and native_rsqrt	2020-02-09 14:42:15 -05:00
libcxx	[libc++] Add availability markup for std::to_chars on Apple platforms	2020-02-17 09:32:46 -05:00
libcxxabi	[libcxxabi] Fix layout of __cxa_exception for win64	2020-02-03 09:55:02 +02:00
libunwind	unwind: rename `__personality_routine` to `_Unwind_Personality_Fn`	2020-02-10 08:52:31 -08:00
lld	[Support] On Windows, ensure hardware_concurrency() extends to all CPU sockets and all NUMA groups	2020-02-14 10:24:22 -05:00
lldb	Separate DIERef vs. user_id_t: m_function_scope_qualified_name_map	2020-02-17 16:35:42 +01:00
llvm	[ARM] Add initial support for Custom Datapath Extension (CDE)	2020-02-17 15:39:16 +00:00
mlir	[mlir] Linalg: Extend promotion to non f32 buffers.	2020-02-17 15:56:49 +01:00
openmp	[openmp][cmake] passing option argument correctly	2020-02-13 09:33:58 -08:00
parallel-libs	…
polly	Revert "[IRBuilder] Virtualize IRBuilder"	2020-02-16 17:01:10 +01:00
pstl	Bump the trunk major version to 11	2020-01-15 13:38:01 +01:00
.arcconfig	Include phabricator.uri in .arcconfig	2020-01-23 11:50:18 -08:00
.clang-format	Add .clang-tidy and .clang-format files to the toplevel of the	2019-01-29 16:43:16 +00:00
.clang-tidy	- Update .clang-tidy to ignore parameters of main like functions for naming violations in clang and llvm directory	2020-01-31 16:49:45 +00:00
.git-blame-ignore-revs	Add LLDB reformatting to .git-blame-ignore-revs	2019-09-04 09:31:55 +00:00
.gitignore	Add a newline at the end of the file	2019-09-04 06:33:46 +00:00
CONTRIBUTING.md	Add contributing info to CONTRIBUTING.md and README.md	2019-12-02 15:47:15 +00:00
README.md	[README] Add note on using cmake to perform the build	2020-02-12 14:51:24 -06:00

README.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 converts it 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:

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
Configure and build LLVM and Clang:
- cd llvm-project
- mkdir build
- cd build
- cmake -G <generator> [options] ../llvm
  
  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, libcxx, libcxxabi, libunwind, lldb, compiler-rt, lld, polly, or debuginfo-tests.
    
    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 . [-- [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.