squiid/llvm
1
0
Fork 0
Code Issues Pull requests Activity
LLVM fork for squiid. https://github.com/llvm/llvm-project/
415006 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
Peter Klausler 3632e9f852 [flang] Accept NULL(mold=x) as constant component value in constant structure constructor 
The predicate IsInitialDataTarget() was failing to return a correct true
result in the case of a reference to the intrinsic function NULL() with a
MOLD= argument.  Fix, and improve tests for "NULL()" elsewhere in semantics,
checking for an attribute set by intrinsics.cpp rather than the actual name.

Differential Revision: https://reviews.llvm.org/D119452
2022-02-14 14:46:53 -08:00
.github github: Fix automated PR creation for backports 2022-02-04 22:22:01 -08:00
bolt [BOLT] Make order of jump table successors deterministic 2022-02-14 10:37:20 -08:00
clang [clang][test] Add -fuse-ld= to test cases added in d238acd113 to resolve test failure with CLANG_DEFAULT_LINKER=lld 2022-02-14 13:21:39 -08:00
clang-tools-extra [clang-tidy] Ignore variable template partial specializations in misc-definitions-in-headers 2022-02-14 11:38:27 +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 Revert "[memprof] Refactor out the MemInfoBlock into a macro based def." 2022-02-14 11:42:58 -08:00
cross-project-tests [dexter] Don't generate results files by default 2022-02-11 15:45:43 +00:00
flang [flang] Accept NULL(mold=x) as constant component value in constant structure constructor 2022-02-14 14:46:53 -08:00
libc [libc] [Obvious] Fix. 2022-02-14 11:56:01 -08:00
libclc libclc: Add clspv64 target 2022-01-13 09:28:19 +00:00
libcxx [libc++] Prepare string.nonmembers for constexpr 2022-02-14 22:53:41 +01:00
libcxxabi [libc++abi] Add a from-scratch testing config for Apple backdeployment 2022-02-14 15:36:50 -05:00
libunwind Update all LLVM documentation mentioning runtimes in LLVM_ENABLE_PROJECTS 2022-02-10 15:05:23 -05:00
lld [WebAssembly] Use GeneralDynamic TLS for exception handling builtins. 2022-02-14 14:08:32 -08:00
lldb [crashlog] Change heuristic to stripping the meta data from crashlogs 2022-02-14 12:18:12 -08:00
llvm [NVPTX] Fix NVPTXReplaceImageHandles for multiple uses of a texref 2022-02-15 01:30:13 +03:00
mlir [OpenMP][IRBuilder] Change the default constructor for OpenMPIRBuilder::LocationDescription 2022-02-15 00:40:34 +05:30
openmp [Libomptarget][NFC] Remove constexpr to hide warnings 2022-02-14 15:34:18 -05:00
polly [polly] Remove uses of PointerType::getElementType() 2022-02-14 10:23:36 +01: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
utils [mlir][sparse] minor cleanup of include placement 2022-02-14 09:16:45 -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
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.