squiid/llvm
1
0
Fork 0
Code Issues Pull requests Activity
LLVM fork for squiid. https://github.com/llvm/llvm-project/
400431 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 8dfbe9b0ae [clang] Make crash reproducer work with clang-cl 
When clang crashes, it writes a standalone source file and shell script
to reproduce the crash.

The Driver used to set `Mode = CPPMode` in generateCompilationDiagnostics()
to force preprocessing mode. This has the side effect of making
IsCLMode() return false, which in turn meant Clang::AddClangCLArgs()
didn't get called when creating the standalone source file, which meant
the stand-alone file was preprocessed with the gcc driver's defaults
In particular, exceptions default to on with the gcc driver, but to
off with the cl driver. The .sh script did use the original command
line, so in the reproducer for a clang-cl crash, the standalone source
file could contain exception-using code after preprocessing that the
compiler invocation in the shell script would then complain about.

This patch removes the `Mode = CPPMode;` line and instead additionally
checks for `CCGenDiagnostics` in most places that check `CCCIsCPP().
This also matches the strategy Clang::ConstructJob() uses to add
-frewrite-includes for creating the standalone source file for a crash
report.

Fixes PR52007.

Differential Revision: https://reviews.llvm.org/D110783
2021-09-30 14:33:14 -04:00
.github
clang [clang] Make crash reproducer work with clang-cl 2021-09-30 14:33:14 -04:00
clang-tools-extra [clangd] Update comment after dea48079b9 2021-09-30 16:45:10 +02:00
compiler-rt Adapt tsan/flush_memory.cpp to run on non-local platforms. 2021-09-29 10:39:38 -07:00
cross-project-tests Reapply "[Dexter] Improve performance by evaluating expressions only when needed" 2021-09-24 10:38:19 +01:00
flang [flang] Front-end and runtime support for CALL EXIT and ABORT 2021-09-30 11:01:22 -07:00
libc [libc] move benchmark function registration to a different file 2021-09-30 13:11:33 +00:00
libclc
libcxx Revert "[libc++][libc++abi] Add tests for vendor-specific properties" 2021-09-30 11:03:59 -07:00
libcxxabi [libc++abi][NFCI] Consistently group new_handler, unexpected_handler and terminate_handler 2021-09-30 14:15:30 -04:00
libunwind [libunwind] Support cfi_undefined and cfi_register for float registers. 2021-09-27 12:04:02 +02:00
lld Second attempt to fix Windows failures from test changes 2021-09-29 19:24:35 -07:00
lldb [lldb] Remove support for replaying the test suite from a reproducer 2021-09-30 10:47:19 -07:00
llvm [AMDGPU] move hasAGPRs/hasVGPRs into header 2021-09-30 10:02:02 -07:00
mlir [mlir][linalg] Fix incorrect bound calculation for tiling conv 2021-09-30 13:50:57 -04:00
openmp [libomptarget] [amdgpu] After a kernel dispatch packet is published, its contents must not be accessed. 2021-09-29 09:22:07 -07:00
parallel-libs
polly [Polly] Check the properties of accesses to operands of a matrix-matrix 2021-09-28 22:58:57 +05:00
pstl
runtimes [libcxx] Add a CI configuration for standalone building in llvm-project/runtimes 2021-09-29 21:37:28 +03:00
utils [mlir] Remove old "tc" linalg ods generator. 2021-09-30 16:30:06 +00:00
.arcconfig
.arclint
.clang-format
.clang-tidy
.git-blame-ignore-revs
.gitignore
.mailmap [mailmap] Add entry for myself 2021-09-22 10:12:16 -04:00
CONTRIBUTING.md
README.md [NFC] Update the list of subprojects in docs. 2021-09-21 17:27:13 +02: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='...' --- semicolon-separated list of the LLVM sub-projects you'd like to additionally build. Can include any of: clang, clang-tools-extra, compiler-rt,cross-project-tests, flang, libc, libclc, libcxx, libcxxabi, libunwind, lld, lldb, mlir, openmp, parallel-libs, polly, or pstl.

        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.