Go to file
Conrad Poelman fc5bf040d8 fix check-clang-tools tests that fail due to Windows CRLF line endings
Running check-clang-tools on Windows produces 5 test failures:

Failed Tests (5):
  Clang Tools :: clang-apply-replacements/ClangRenameClassReplacements.cpp
  Clang Tools :: clang-apply-replacements/basic.cpp
  Clang Tools :: clang-apply-replacements/format.cpp
  Clang Tools :: clang-move/move-used-helper-decls.cpp
  Clang Tools :: clang-tidy/infrastructure/export-diagnostics.cpp

Four of these failures are simply due to fixed character position
offsets differing on Windows versus Linux, since Windows line endings
take up two characters instead of one:

clang-apply-replacements/ClangRenameClassReplacements.cpp runs clang-rename -offset=254
clang-apply-replacements/Inputs/basic/file[12].yaml specify e.g.  FileOffset: 148 and Offset: 298
clang-apply-replacements/Inputs/format/{no,yes}.yaml specify e.g.  FileOffset: 94 and Offset: 94
clang-tidy/infrastructure/export-diagnostics.cpp specifies e.g.  CHECK-YAML-NEXT: FileOffset: 30

(The move-used-helper-decls.cpp failure seems more complex; clang-move
adds a blank line after void HelperFun1() {} when
clang-move/Inputs/helper_decls_test.cpp has LF line endings, but does
not add a blank line when the input files has CRLF line endings. That
difference in behavior seems like it may be an actual bug, but I have
yet to track it down.)

Differential Revision: https://reviews.llvm.org/D97625
2022-02-11 15:23:51 -07:00
.github github: Fix automated PR creation for backports 2022-02-04 22:22:01 -08:00
bolt Cleanup LLVMObject headers 2022-02-10 21:13:44 +01:00
clang Reland "[lld/coff] Make lld-link work in a non-MSVC shell, add /winsysroot:" 2022-02-11 17:07:33 -05:00
clang-tools-extra [clang-tidy] Add early exit for defaulted FunctionDecls 2022-02-10 20:29:26 +01:00
cmake [cmake] Partially deduplicate `{llvm,compiler_rt}_check_linker_flag` for runtime libs and llvm 2022-01-29 06:07:24 +00:00
compiler-rt [sanitizers] Add missing header to fix Fuchsia builds 2022-02-11 21:58:02 +00:00
cross-project-tests [dexter] Don't generate results files by default 2022-02-11 15:45:43 +00:00
flang [flang] Upstream fix to allocmem codegen to deal with missing dimensions 2022-02-11 11:12:49 -08:00
libc [libc][obvious] only include vector with malloc 2022-02-10 11:17:35 -08:00
libclc libclc: Add clspv64 target 2022-01-13 09:28:19 +00:00
libcxx [libc++] Prepare string.ops for constexpr 2022-02-11 22:31:32 +01:00
libcxxabi [demangler] Adjust unqualified name parsing 2022-02-11 04:22:06 -08:00
libunwind Update all LLVM documentation mentioning runtimes in LLVM_ENABLE_PROJECTS 2022-02-10 15:05:23 -05:00
lld Reland "[lld/coff] Make lld-link work in a non-MSVC shell, add /winsysroot:" 2022-02-11 17:07:33 -05:00
lldb Revert "Add -fmodules-local-submodule-visibility to MANDATORY_MODULE_BUILD_CFLAGS" 2022-02-10 15:37:11 -08:00
llvm m68k: Support bit shifts on 64-bit integers 2022-02-12 06:11:49 +08:00
mlir [mlir][bufferize] Use rewriter instead of replacing all uses directly 2022-02-12 02:35:36 +09:00
openmp [OpenMP] libomp: fix bug in implementation of distribute construct. 2022-02-11 17:34:26 +03:00
polly [SCEV] `createNodeForSelectOrPHIInstWithICmpInstCond()`: generalize eq handling 2022-02-11 21:58:19 +03:00
pstl Bump the trunk major version to 15 2022-02-01 23:54:52 -08:00
runtimes [runtimes] rewrap a comment to 80 columns 2022-02-10 20:57:13 -05:00
test fix check-clang-tools tests that fail due to Windows CRLF line endings 2022-02-11 15:23:51 -07:00
third-party Ensure newlines at the end of files (NFC) 2021-12-26 08:51:06 -08:00
utils Revert "[lld/coff] Make lld-link work in a non-MSVC shell, add /winsysroot:" 2022-02-11 13:07:23 -08:00
.arcconfig
.arclint
.clang-format
.clang-tidy [clangd] Cleanup of readability-identifier-naming 2022-02-01 13:31:52 +00:00
.git-blame-ignore-revs
.gitignore
.mailmap
CONTRIBUTING.md docs: update some bug tracker references (NFC) 2022-01-10 15:59:08 -08:00
README.md Update all LLVM documentation mentioning runtimes in LLVM_ENABLE_PROJECTS 2022-02-10 15:05:23 -05:00
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='...' and -DLLVM_ENABLE_RUNTIMES='...' --- semicolon-separated list of the LLVM sub-projects and runtimes you'd like to additionally build. LLVM_ENABLE_PROJECTS can include any of: clang, clang-tools-extra, cross-project-tests, flang, libc, libclc, lld, lldb, mlir, openmp, polly, or pstl. LLVM_ENABLE_RUNTIMES can include any of libcxx, libcxxabi, libunwind, compiler-rt, libc or openmp. Some runtime projects can be specified either in LLVM_ENABLE_PROJECTS or in LLVM_ENABLE_RUNTIMES.

        For example, to build LLVM, Clang, libcxx, and libcxxabi, use -DLLVM_ENABLE_PROJECTS="clang" -DLLVM_ENABLE_RUNTIMES="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). Be careful if you install runtime libraries: if your system uses those provided by LLVM (like libc++ or libc++abi), you must not overwrite your system's copy of those libraries, since that could render your system unusable. In general, using something like /usr is not advised, but /usr/local is fine.

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

Getting in touch

Join LLVM Discourse forums, discord chat or #llvm IRC channel on OFTC.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.