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

Find a file

Louis Dionne ce565861c7 [libc++] Drop old workaround for iostreams instantiations missing from the dylib On old Apple platforms (pre 10.9), we couldn't rely on the iostreams explicit instantiations being part of the dylib. However, we don't support back-deploying to such old deployment targets anymore, so the workaround can be dropped.		2020-10-22 14:51:25 -04:00
clang	[SystemZ][z/OS] Set short-enums as the default for z/OS	2020-10-22 14:15:58 -04:00
clang-tools-extra	clang/Basic: Remove ContentCache::getRawBuffer, NFC	2020-10-22 14:00:44 -04:00
compiler-rt	[MemProf] Allow the binary to specify the profile output filename	2020-10-22 08:30:19 -07:00
debuginfo-tests	[Dexter][NFC] Add Missing Commands to Commands.md Contents	2020-10-19 16:38:49 +01:00
flang	[flang] Another validity of the TARGET= argument of ASSOCIATED() for objects	2020-10-21 10:17:27 -07:00
libc	[libc] Add LLVM libc specific functions to llvm_libc_ext.td.	2020-10-19 18:21:25 +00:00
libclc	libclc: Use find_package to find Python 3 and require it	2020-10-01 22:31:33 +02:00
libcxx	[libc++] Drop old workaround for iostreams instantiations missing from the dylib	2020-10-22 14:51:25 -04:00
libcxxabi	[libcxxabi] Define _LIBCXXABI_WEAK properly for mingw compilers	2020-10-22 09:00:57 +03:00
libunwind	[take 2] [libc++] Include <__config_site> from <__config>	2020-10-21 10:40:33 -04:00
lld	[ELF] Set SHF_INFO_LINK for .rel[a].plt and .rel[a].dyn	2020-10-22 09:48:19 -07:00
lldb	Revert "[lldb] Explicitly use the configuration architecture when building test executables"	2020-10-22 18:42:19 +02:00
llvm	[InstCombine][NFC] Use ConstantExpr::getBinOpIdentity	2020-10-22 20:44:57 +02:00
mlir	[mlir] Do not start threads in AsyncRuntime	2020-10-22 08:31:30 -07:00
openmp	[libomptarget] Require LLVM source tree to build libomptarget	2020-10-21 18:53:00 +01:00
parallel-libs
polly	Remove .svn from exclude list as we moved to git	2020-10-21 16:09:21 +02:00
pstl
utils/arcanist	Fix arc lint's clang-format rule: only format the file we were asked to format.	2020-10-11 14:24:23 -07:00
.arcconfig
.arclint
.clang-format
.clang-tidy
.git-blame-ignore-revs	NFC: Add whitespace-changing revisions to .git-blame-ignore-revs	2020-09-21 20:17:24 -04:00
.gitignore
CONTRIBUTING.md
README.md	Revert "This is a test commit"	2020-10-21 09:34:15 +08: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.