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

Find a file

Daniel McIntosh 9403b59a7d [test] Fix apparent typo in clang/test/Driver/std.c Currently the test on line 3 is identical to the test on line 1. Looking at the rest of the file (particularily the use of FOVERRIDE as the check-prefix), I think it's pretty clear that this line was supposed to use `-ftrigraphs` instead of `-trigraphs`. Reviewed By: thakis Differential Revision: https://reviews.llvm.org/D97796		2021-03-03 10:31:47 -05:00
.github
clang	[test] Fix apparent typo in clang/test/Driver/std.c	2021-03-03 10:31:47 -05:00
clang-tools-extra	[clangd] Make WorkspaceSymbols request work with empty queries	2021-03-03 15:41:39 +01:00
compiler-rt	Revert "[InstrProfiling] Place __llvm_prf_vnodes and __llvm_prf_names in llvm.used on ELF"	2021-03-03 10:21:17 -05:00
debuginfo-tests	Fix `debuginfo-tests/llvm-prettyprinters` build after MLIR API change in `e6260ad043` (NFC)	2021-03-02 19:21:03 +00:00
flang	[flang] Detect circularly defined interfaces of procedures	2021-03-02 15:18:12 -08:00
libc	[libc][NFC] Exclude few targets from the `all` target.	2021-02-24 08:59:55 -08:00
libclc
libcxx	[libc++] Add bind_front function (P0356R5).	2021-03-02 16:18:06 -08:00
libcxxabi	[libc++/abi] Allow running back-deployment testing against libc++abi	2021-03-01 12:13:03 -05:00
libunwind	[libunwind] [risc-v] This patch is for fixing	2021-03-03 04:32:47 +05:30
lld	[lld][MachO] Silence "enumeral and non-enumeral type" warning from gcc	2021-03-03 10:39:35 +01:00
lldb	[lldb][NFC] Delete unused AddressResolverName	2021-03-03 13:30:02 +01:00
llvm	Revert "[InstrProfiling] Place __llvm_prf_vnodes and __llvm_prf_names in llvm.used on ELF"	2021-03-03 10:21:17 -05:00
mlir	[mlir][Shape] Make shape_eq nary	2021-03-03 16:26:40 +01:00
openmp	[OpenMP] Add allocator support for target memory	2021-03-02 16:45:12 -06:00
parallel-libs
polly	[Polly] Refabricating IsOutermostParallel() from Integer Set Libarary(ISL) to take the C++ wrapper	2021-03-03 01:49:37 -06:00
pstl
runtimes	[runtimes] Use standalone build only for compiler-rt	2021-03-03 00:06:20 -08:00
utils/arcanist
.arcconfig	Add modern arc config for default "onto" branch	2021-02-22 11:58:13 -08:00
.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
- 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, 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 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.