LLVM fork for squiid. https://github.com/llvm/llvm-project/

Find a file

Peter Steinfeld 2cf52504bb [flang] Fixes for RESHAPE() I fixed an assert caused by passing an empty array as the source= argument to RESHAPE(). In the process, I noticed that there were no tests for RESHAPE(), so I wrote a test that covers all the description in 16.9.163. In the process, I made the error messages more consistent and descriptive. I also changed the test to see if a reference to an intrinsic function was a constant to say that it is a constant if it's a refererence to an invalid intrinsic. This avoids emitting multiple messages for the same erroneous source. Differential Revision: https://reviews.llvm.org/D84904		2020-07-30 19:05:06 -07:00
clang	[clang codegen][AArch64] Use llvm.aarch64.neon.fcvtzs/u where it's necessary	2020-07-30 15:41:54 -07:00
clang-tools-extra	[clang-tidy][NFC] Use StringMap for ClangTidyCheckFactories::FacoryMap	2020-07-30 22:57:33 +01:00
compiler-rt	[profile] Remove dependence on getpagesize from InstrProfilingBuffer.c.o	2020-07-30 16:22:40 -07:00
debuginfo-tests
flang	[flang] Fixes for RESHAPE()	2020-07-30 19:05:06 -07:00
libc	[libc] Add a tool called WrapperGen.	2020-07-30 16:07:26 -07:00
libclc
libcxx	[libc++] Use generator expression in Linker script generation	2020-07-30 11:59:29 -04:00
libcxxabi
libunwind	[libunwind] Provide a way to set '_LIBUNWIND_IS_BAREMETAL' through cmake.	2020-07-29 11:48:28 +01:00
lld	[COFF] Port CallGraphSort to COFF from ELF	2020-07-30 15:21:44 -07:00
lldb	[debugserver/Apple Silicon] Handoff connections when attaching to translated processes	2020-07-30 16:21:05 -07:00
llvm	[ValueTracking] Remove AllocaForValue parameter	2020-07-30 18:48:34 -07:00
mlir	[MLIR][NFC] Add SymbolUse::UseRange::empty()	2020-07-30 15:18:58 -07:00
openmp	[OpenMP] Refactored the function `targetDataEnd`	2020-07-30 21:39:26 -04:00
parallel-libs
polly	Reland "[SCEVExpander] Add option to preserve LCSSA directly."	2020-07-29 20:41:53 +01:00
pstl	[libc++][pstl] Remove c++98 from UNSUPPORTED annotations	2020-07-29 14:17:32 -04:00
utils/arcanist
.arcconfig
.arclint
.clang-format
.clang-tidy
.git-blame-ignore-revs
.gitignore
CONTRIBUTING.md
README.md

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.