| /llvm-project/clang/docs/ |
| H A D | HowToSetupToolingForLLVM.rst | 7 of specific tools using this infrastructure (e.g. ``clang-check``). This
14 Clang Tooling needs a compilation database to figure out specific build
17 invoking clang tools, you can either specify a path to a build directory
18 using a command line parameter ``-p`` or let Clang Tooling find this
20 build using CMake to use clang tools.
25 If you intend to use make to build LLVM, you should have CMake 2.8.6 or
29 make a build directory and run CMake from it:
31 .. code-block:: console
33 $ mkdir your/build/directory
34 $ cd your/build/directory
[all …]
|
| /llvm-project/llvm/utils/ |
| H A D | check_ninja_deps.py | 3 # ======- check-ninja-deps - build debugging script ----*- python -*--========#
7 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
9 # ==------------------------------------------------------------------------==#
11 """Script to find missing formal dependencies in a build.ninja file.
15 executed after the Tablegen build step that generates the header. So the
16 dependency graph in build.ninja should have the Tablegen build step as an
17 ancestor of the C++ one. If it does not, then there's a latent build-failure
18 bug, because depending on the order that ninja chooses to schedule its build
19 steps, the C++ build step could run first, and fail because the header it needs
23 not notice, if your local test build happens to succeed. What you'd like is a
[all …]
|
| /llvm-project/flang/docs/ |
| H A D | GettingStarted.md | 1 <!--===- docs/GettingStarted.md
5 SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 -->
12 ---
14 ---
18 There are two ways to build flang. The first method is to build it at the same
19 time that you build all of the projects on which it depends. This is called
20 building in tree. The second method is to first do an in tree build to create
22 build, only build the flang code itself. This is called building standalone.
24 create the base build and base install areas, you can create multiple
[all …]
|
| /llvm-project/llvm/utils/release/ |
| H A D | build_llvm_release.bat | 8 echo used for the releases at https://github.com/llvm/llvm-project/releases
10 echo Usage: build_llvm_release.bat --version ^<version^> [--x86,--x64, --arm64] [-
[all...] |
| /llvm-project/.github/workflows/ |
| H A D | docs.yml | 4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
6 name: "Test documentation build"
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
18 - 'clang/include/clang/Basic/AttrDocs.td'
19 - 'clan
[all...] |
| H A D | release-binaries.yml | 6 release-version:
15 runs-on:
16 description: "Runner to use for the build"
20 - ubuntu-22.04
21 - ubuntu-22.04-arm
22 - macos-1
[all...] |
| H A D | llvm-project-tests.yml | 17 default: '["ubuntu-latest", "windows-2019", "macOS-13"]'
40 # Use windows-2019 due to:
41 # https://developercommunity.visualstudio.com/t/Prev-Issue---with-__assume-isna
[all...] |
| /llvm-project/llvm/docs/ |
| H A D | AdvancedBuilds.rst | 2 Advanced Build Configurations
11 `CMake <http://www.cmake.org/>`_ is a cross-platform build-generator tool. CMake
12 does not build the project, it generates the files needed by your build tool
22 Many of the build configurations mentioned on this documentation page can be
24 file that sets the necessary flags for a specific build configuration. The caches
26 can be passed to CMake using the :code:`-C` flag as demonstrated in the examples
32 The Clang CMake build system supports bootstrap (aka multi-stage) builds. At a
33 high level a multi-stage build is a chain of builds that pass data from one
35 bootstrap build.
37 In a simple two-stage bootstrap build, we build clang using the system compiler,
[all …]
|
| H A D | MyFirstTypoFix.rst | 26 - know how to use an editor,
28 - have basic C++ knowledge,
30 - know how to install software on your system,
32 - are comfortable with the command line,
34 - have basic knowledge of git.
38 -----
[all...] |
| /llvm-project/lldb/docs/resources/ |
| H A D | fuzzing.rst | 5 --------
10 --------------------
12 …build configuration that has the address sanitizer and sanitizer coverage enabled. In addition to …
16 -DLLVM_USE_SANITIZER='Address' \
17 -DLLVM_USE_SANITIZE_COVERAGE=On \
18 -DCLANG_ENABLE_PROTO_FUZZER=ON
20 …zzer's sanitizer coverage is available here: `<https://llvm.org/docs/LibFuzzer.html#fuzzer-usage>`_
22 If you want to debug LLDB itself when you find a bug using the fuzzers, use the CMake option ``-DCM…
24 To build a fuzzer, run the desired ninja command for the fuzzer(s) you want to build:
28 $ ninja lldb-target-fuzzer
[all …]
|
| H A D | build.rst | 5 ----------
[all...] |
| /llvm-project/flang/ |
| H A D | .drone.star | 4 "name": "%s-clang" % arch,
10 …"apt-get update && apt-get install -y clang-8 cmake ninja-build lld-8 llvm-8-dev libc++-8-dev libc…
11 … "git clone --depth=1 -b f18 https://github.com/flang-compiler/f18-llvm-project.git llvm-project",
12 "mkdir llvm-project/build && cd llvm-project/build",
13 …-8 CXX=clang++-8 CXXFLAGS="-stdlib=libc++" LDFLAGS="-fuse-ld=lld" cmake -GNinja -DCMAKE_BUILD_TYPE…
14 "ninja install",
16 "mkdir build && cd build",
17 …-8 CXX=clang++-8 CXXFLAGS="-UNDEBUG -stdlib=libc++" LDFLAGS="-fuse-ld=lld" cmake -GNinja -DCMAKE_B…
18 "ninja -j8",
19 "ctest --output-on-failure -j24",
[all …]
|
| /llvm-project/libc/docs/ |
| H A D | full_cross_build.rst | 4 Full Cross Build
16 In this document, we will present recipes to cross build the full libc. When we
17 say *cross build* a full libc, we mean that we will build the full libc for a
22 There are two main recipes to cross build the full libc. Each one serves a
26 * **Standalone cross build** - Using this recipe one can build the libc using a
28 build for the host as well as the target.
29 * **Bootstrap cross build**
[all...] |
| H A D | overlay_mode.rst | 24 overlay mode. In both the ways, we build a static archive named
31 Building LLVM-libc as a standalone runtime
32 --------
[all...] |
| /llvm-project/bolt/docs/ |
| H A D | OptimizingClang.md | 11 large applications measuring over hundreds of megabytes in size. However, medium-sized
12 programs can benefit too. Clang, one of the most popular open-source C/C++ compilers,
15 misses and can be significantly improved with BOLT, even on top of profile-guided and
16 link-time optimizations.
18 In this tutorial we will first build Clang with PGO and LTO, and then will show steps on how to
20 the compile-time performance gains are coming from, and verify that the speed-ups are
25 The process of getting Clang sources and performing the build is very similar to the
27 on how to obtain and build Clang in [Bootstrapping Clang-
[all...] |
| /llvm-project/libcxx/docs/ |
| H A D | BuildingLibcxx.rst | |
| /llvm-project/libc/config/windows/ |
| H A D | README.md | 5 To build LLVM libc on Windows, first build Clang using the following steps.
9 successful clang build.
21 [Ninja](https://github.com/ninja-build/ninja/releases). (Optional, included
24 crucial as it allows you to use build tools like CMake and Ninja:
27 …"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Auxiliary\Build\vcvarsall.bat" a…
34 [Git](https://git-scm.com/download/win) for Windows. Check out the LLVM
38 git clone https://github.com/llvm/llvm-project.git
48 libc, and finally, build and test the libc.
50 8. Create a empty build directory in `C:\src` or your preferred directory and
54 mkdir libc-build
[all …]
|
| /llvm-project/compiler-rt/lib/tsan/ |
| H A D | check_cmake.sh | 2 set -u
3 set -e
6 if [ -d "$ROOT/llvm-build" ]; then
7 cd $ROOT/llvm-build
9 mkdir -p $ROOT/llvm-build
10 cd $ROOT/llvm-build
11 …CC=clang CXX=clang++ cmake -G Ninja -DLLVM_ENABLE_WERROR=ON -DCMAKE_BUILD_TYPE=Release -DLLVM_ENAB…
13 ninja
14 ninja check-sanitizer
15 ninja check-tsan
[all …]
|
| /llvm-project/llvm/utils/docker/debian10/ |
| H A D | Dockerfile | |
| /llvm-project/libc/docs/gpu/ |
| H A D | building.rst | 14 This document will present recipes to build the LLVM C library targeting a GPU
15 architecture. The GPU build uses the same :ref:`cross build<full_cross_build>`
17 it *must* be built with an up-to-date ``clang`` compiler. This is because the
21 ``nvptx64-nvidia-cuda`` for NVIDIA GPUs or ``amdgcn-amd-amdhsa`` for AMD GPUs.
22 Targeting these architectures is done through ``clang``'s cross-compilin
[all...] |
| H A D | testing.rst | 21 depending on the build configuration. The GPU target is considered a full build
22 and therefore provides all of its own utilities to build and run the generated
25 #. **Hermetic tests** - These are unit tests built with a test suite similar to
27 tests except that the entire environment is self-hosted. This allows us to
31 #. **Integration tests** - These are lightweight tests that simply call a
32 ``main`` function and checks if it returns non-zero. These are primarily used
47 --------------
57 .. code-block:: c++
76 --------------
80 kernels on the given device. Currently we provide the ``amdhsa-loader`` and
[all …]
|
| /llvm-project/libc/src/math/docs/ |
| H A D | add_math_function.md | 1 # How to add a new math function to LLVM-libc
14 - Add entry points `libc.src.math.func` to the following files:
19 - Add function specs to the file:
29 - Add `add_math_entrypoint_object(<func>)` to:
33 - Add function declaration (under `LIBC_NAMESPACE` namespace) to:
37 - Add function definition to:
41 - Add the corresponding `add_entrypoint_object` to:
45 - Add architectural specific implementations to:
52 - Floating point utilities and math functions that are also used internally are
57 - Thes
[all...] |
| /llvm-project/polly/www/ |
| H A D | get_started.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
5 <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
6 <title>Polly - Getting Started</title>
13 <!--#include virtual="menu.html.incl"-->
[all...] |
| /llvm-project/libcxx/utils/ci/ |
| H A D | run-buildbot | 2 # ===----------
[all...] |
| /llvm-project/clang/utils/analyzer/ |
| H A D | entrypoint.py | 12 cmake_opts = ["-D" + cmd for cmd in settings.D]
29 def parse_arguments() -> Tuple[argparse.Namespace, List[str]]:
31 parser.add_argument("--wait", action="store_true")
32 parser.add_argument("--build-llvm", action="store_true")
33 parser.add_argument("--build-llvm-only", action="store_true")
34 parser.add_argument("-D", action="append", default=[])
39 os.chdir("/build")
43 ninja()
45 print("Build failed!")
50 return "build.ninja" not in os.listdir()
[all …]
|