squiid/llvm
1
0
Fork 0
Code Issues Pull requests Activity
LLVM fork for squiid. https://github.com/llvm/llvm-project/
398399 commits 3 branches 0 tags 2 GiB
C++ 40.8%
LLVM 34.3%
C 12.6%
Assembly 8.2%
Python 1.1%
Other 2.6%
Find a file
Nico Weber b32506cb86 Revert "[gn build] Add a file that should have been in cfe02847496b856aa" 
This reverts commit 6be7f5c354.
We'll need this file eventually, but it in fact shouldn't have been in
cfe0284749. It's currently unreferenced.
2021-09-07 17:01:48 -04:00
.github
clang [MC] Add MCSubtargetInfo to MCAlignFragment 2021-09-07 15:46:19 +01:00
clang-tools-extra [clangd] Omit default template arguments from type hints 2021-09-07 02:38:27 -04:00
compiler-rt Greedy set cover implementation of Merger::Merge 2021-09-07 09:42:38 -07:00
cross-project-tests
flang [flang] evaluate: Fold SQRT, HYPOT, & CABS 2021-09-07 10:33:11 -07:00
libc [libc][Obvious] Reorder CMakelists alphabetically. 2021-09-05 11:01:05 +08:00
libclc
libcxx [libc++][NFC] Add missing synopsis for node handles 2021-09-07 15:26:33 -04:00
libcxxabi
libunwind
lld [ELF][test] Improve gitBitcodeMachineKind tests 2021-09-07 11:38:43 -07:00
lldb [gn build] Add build files for LLDB 2021-09-07 15:25:04 -04:00
llvm Revert "[gn build] Add a file that should have been in cfe02847496b856aa" 2021-09-07 17:01:48 -04:00
mlir Improve error message when creating an op that isn't registered in the context 2021-09-07 20:42:30 +00:00
openmp [OpenMP][libomptarget][NFC] Change checkDeviceAndCtors return type to bool. 2021-09-07 13:59:27 -05:00
parallel-libs
polly
pstl
runtimes
utils [Bazel] Add missing dependency after 650bbc5620 2021-09-05 21:14:05 +02:00
.arcconfig
.arclint
.clang-format
.clang-tidy
.git-blame-ignore-revs
.gitignore
.mailmap
CONTRIBUTING.md
README.md
SECURITY.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 convert them 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:

  1. 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

  2. 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 cross-project-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.