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

Find a file

Fangrui Song cfe9ccbddd [libc++abi] Simplify scan_eh_tab 1. All `_URC_HANDLER_FOUND` return values need to set `landingPad` and its value does not matter for `_URC_CONTINUE_UNWIND`. So we can always set `landingPad` to unify code. 2. For an exception specification (`ttypeIndex < 0`), we can check `_UA_FORCE_UNWIND` first. 3. The so-called type 3 search (`actions & _UA_CLEANUP_PHASE && !(actions & _UA_HANDLER_FRAME)`) is actually conceptually wrong. For a catch handler or an unmatched dynamic exception specification, `_UA_HANDLER_FOUND` should be returned immediately. It still appeared to work because the `ttypeIndex==0` case would return `_UA_HANDLER_FOUND` at a later time. This patch fixes the conceptual error and simplifies the code by handling type 3 the same way as type 2 (which is also what libsupc++ does). The only difference between phase 1 and phase 2 is what to do with a cleanup (`actionEntry==0`, or a `ttypeIndex==0` is found in the action record chain): phase 1 returns `_URC_CONTINUE_UNWIND` while phase 2 returns `_URC_HANDLER_FOUND`. Reviewed By: #libc_abi, compnerd Differential Revision: https://reviews.llvm.org/D93190		2021-01-21 15:19:23 -08:00
.github	[github] Move repo lockdown config into llvm-project repo	2021-01-11 16:20:08 -08:00
clang	Fix crash when emitting NullReturn guards for functions returning BOOL	2021-01-21 14:29:36 -08:00
clang-tools-extra	[clangd] Fix a missing override keyword, NFC.	2021-01-21 11:06:43 +01:00
compiler-rt	[MSan] Move origins for overlapped memory transfer	2021-01-21 02:11:26 +00:00
debuginfo-tests	[DebugInfo][dexter] Tweak dexter test for merged values	2021-01-19 12:45:31 +00:00
flang	[flang] Better C_LOC and C_ASSOCIATED in flang/module	2021-01-21 09:41:05 -08:00
libc	[libc][NFC][obvious] fix the names of MPFR tests	2021-01-20 23:42:01 +00:00
libclc
libcxx	[libc++] Use ioctl when available to get random_device entropy.	2021-01-21 18:01:02 +01:00
libcxxabi	[libc++abi] Simplify scan_eh_tab	2021-01-21 15:19:23 -08:00
libunwind	[CMake] Remove dead code setting policies to NEW	2021-01-19 17:19:36 +02:00
lld	[ELF] report section sizes when output file too large	2021-01-21 19:47:03 +00:00
lldb	[lldb-vscode] improve modules request	2021-01-21 13:18:50 -08:00
llvm	[llvm-mca] Initial implementation of serialization using JSON. The views	2021-01-21 15:15:54 -08:00
mlir	Add Python bindings for the builtin dialect	2021-01-21 22:44:44 +00:00
openmp	[OpenMP] Fix failing test due to change in offloading flags	2021-01-21 14:09:36 -05:00
parallel-libs
polly	[polly][NewPM][test] Fix polly tests under -enable-new-pm	2021-01-19 12:38:58 -08:00
pstl	[pstl] Replace direct use of assert() with _PSTL_ASSERT	2020-11-02 18:35:54 -05:00
runtimes	[MSVC] Don't add -nostdinc++ -isystem to runtimes builds	2021-01-15 13:22:07 -08:00
utils/arcanist
.arcconfig	Set the target branch for `arc land` to main	2020-12-07 21:57:32 +00:00
.arclint
.clang-format
.clang-tidy
.git-blame-ignore-revs
.gitignore	Reland [lldb][docs] Use sphinx instead of epydoc to generate LLDB's Python reference	2021-01-17 12:13:01 +01:00
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.