Home
last modified time | relevance | path

Searched +full:clang +full:- +full:build (Results 1 – 25 of 1041) sorted by relevance

12345678910>>...42

/llvm-project/.github/workflows/
H A Ddocs.yml4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
6 name: "Test documentation build"
14 - 'main'
16 - 'llvm/docs/**'
17 - 'clang/docs/**'
18 - 'clan
[all...]
/llvm-project/llvm/docs/
H A DAdvancedBuilds.rst2 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
25 for Clang are located in :code:`/clang/cmake/caches` within the monorepo. They
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.
[all …]
H A DHowToBuildWithPGO.rst2 How To Build Clang and LLVM with Profile-Guided Optimizations
8 PGO (Profile-Guided Optimization) allows your compiler to better optimize code
9 for how it actually runs. Users report that applying this to Clang and LLVM can
12 This guide walks you through how to build Clang with PGO, though it also applies
15 If you want to build other software with PGO, see the `end-user documentation
16 for PGO <https://clang.llvm.org/docs/UsersManual.html#profile-guided-optimization>`_.
22 See https://llvm.org/docs/AdvancedBuilds.html#multi-stage-pgo
28 tested on a few Linux flavors, and requires a checkout of LLVM, Clang, and
29 compiler-rt. Despite the name, it performs four clean builds of Clang, so it
30 can take a while to run to completion. Please see the script's ``--help`` for
[all …]
H A DMyFirstTypoFix.rst19 We'll be making a change to Clang, but the steps for other parts of LLVM are the same.
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...]
H A DDocker.rst7 You can find a number of sources to build docker images with LLVM components in
8 ``llvm/utils/docker``. They can be used by anyone who wants to build the docker
12 We currently provide Dockerfiles with ``debian12`` and ``nvidia-cuda`` base images.
17 ----
24 ---
[all...]
H A DGettingStarted.rst19 C-like languages use the `Clang <https://clang.llvm.org/>`_ front end. This
21 -- and from there into object files, using LLVM.
32 #. Check out LLVM (including subprojects like Clang):
34 * ``git clone https://github.com/llvm/llvm-project.git``
37 ``git clone --config core.autocrlf=false
38 https://github.com/llvm/llvm-projec
[all...]
/llvm-project/flang/docs/
H A DGettingStarted.md1 <!--===- 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/utils/bazel/
H A D.bazelrc3 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
11 # https://github.com/llvm/llvm-project/issues/55924
12 common --enable_bzlmod=false --enable_workspace
15 common -
[all...]
/llvm-project/clang/docs/
H A DHowToSetupToolingForLLVM.rst2 How To Setup Clang Tooling For LLVM
5 Clang Tooling provides infrastructure to write tools that need syntactic
7 of specific tools using this infrastructure (e.g. ``clang-check``). This
8 document provides information on how to set up and use Clang Tooling for
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.
22 Setup Clang Tooling Using CMake and Make
25 If you intend to use make to build LLVM, you should have CMake 2.8.6 or
[all …]
/llvm-project/libc/docs/gpu/
H A Dbuilding.rst14 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-amdhs
[all...]
/llvm-project/libc/docs/
H A Dfull_cross_build.rst4 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 Dfull_host_build.rst4 Full Host Build
16 In this document, we will present a recipe to build the full libc for the host.
17 When we say *build the libc for the host*, the goal is to build the libc for
19 build for developing LLVM-libc, then we will explain how to build LLVM-libc as
22 Configure the build for development
26 Below is the list of commands for a simple recipe to build LLV
[all...]
/llvm-project/bolt/docs/
H A DOptimizingClang.md1 # Optimizing Clang : A Practical Example of Applying BOLT
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,
14 As we will see, the Clang binary suffers from many instruction cache
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
19 apply BOLT optimizations to make Clang u
[all...]
/llvm-project/clang/tools/clang-fuzzer/
H A DREADME.txt1 This directory contains three utilities for fuzzing Clang: clang-fuzzer,
2 clang-objc-fuzzer, and clang-proto-fuzzer. All use libFuzzer to generate inputs
3 to clang via coverage-guided mutation.
5 The three utilities differ, however, in how they structure inputs to Clang.
6 clang-fuzzer makes no attempt to generate valid C++ programs and is therefore
7 primarily useful for stressing the surface layers of Clang (i.e. lexer, parser).
9 clang-objc-fuzzer is similar but for Objective-C: it makes no attempt to
10 generate a valid Objective-C program.
12 clang-proto-fuzzer uses a protobuf class to describe a subset of the C++
13 language and then uses libprotobuf-mutator to mutate instantiations of that
[all …]
/llvm-project/clang/test/ClangScanDeps/
H A Doptimize-vfs-pch.m3 // RUN: rm -rf %t
4 // RUN: split-file %s %t
5 // RUN: sed -e "s|DIR|%/t|g" %t/build/compile-commands-pch.json.in > %t/build/compile-commands-pch.…
6 // RUN: sed -e "s|DIR|%/t|g" %t/build/compile-commands-tu.json.in > %t/build/compile-commands-tu.js…
7 // RUN: sed -e "s|DIR|%/t|g" %t/build/compile-commands-tu-no-vfs-error.json.in > %t/build/compile-c…
8 // RUN: sed -e "s|DIR|%/t|g" %t/build/compile-commands-tu1.json.in > %t/build/compile-commands-tu1.…
9 // RUN: sed -e "s|DIR|%/t|g" %t/build/pch-overlay.yaml.in > %t/build/pch-overlay.yaml
11 // RUN: clang-scan-deps -compilation-database %t/build/compile-commands-pch.json \
12 // RUN: -j 1 -format experimental-full --optimize-args=vfs,header-search > %t/pch-deps.db
13 // RUN: %deps-to-rsp %t/pch-deps.db --module-name=A > %t/A.rsp
[all …]
H A Doptimize-vfs.m1 // RUN: rm -rf %t
2 // RUN: split-file %s %t
3 // RUN: sed -e "s|DIR|%/t|g" %t/build/compile-commands.json.in > %t/build/compile-commands.json
4 // RUN: sed -e "s|DIR|%/t|g" %t/build/vfs.yaml.in > %t/build/vf
[all...]
/llvm-project/mlir/utils/clang-tidy/
H A DREADME.md1 ### Apply clang-tidy fixes on the repo
3 This script runs clang-tidy on every C++ source file in MLIR and commit
7 The advised way to use this is to build clang-tidy (in release mode) and
8 have another build directory for MLIR. Here is a sample invocation from
13 CLANG_TIDY=build-clang/bin/clang-tidy \
15 ./mlir/utils/clang-tidy/apply-clang-tidy.sh build mlir ~/clang-tidy-fails/
16 } 2>&1 | tee ~/clang-tidy.log
19 - `build-clang/` contains the result of a build of clang-tidy, configured
23 -DLLVM_ENABLE_PROJECTS="clang;mlir;clang-tools-extra" \
24 -DCMAKE_BUILD_TYPE=Release \
[all …]
/llvm-project/libc/config/windows/
H A DREADME.md5 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
41 7. Ensure you have access to Clang, either by downloading from
43 [building it yourself](https://clang.llvm.org/get_started.html).
47 In this section, Clang will be used to compile LLVM
[all …]
/llvm-project/clang/tools/scan-build-py/
H A DREADME.md1 scan-build
4 A package designed to wrap a build so that all calls to gcc/clang are
6 the clang static analyzer. Includes intercept-build tool, which logs
7 the build, as well as scan-build tool, which logs the build and runs
8 the clang static analyzer on it.
11 -----------
15 - It has been tested on FreeBSD, GNU/Linux and OS X.
16 - Prepared to work on windows, but need help to make it.
20 -------------
26 ----------
[all …]
/llvm-project/clang/test/Driver/
H A Driscv-default-build-attributes.s2 // RUN: %clang --target=riscv32 -### %s 2>&1 \
3 // RUN: | FileCheck %s --check-prefix=CHECK-ENABLED
4 // RUN: %clang --target=riscv64 -### %s 2>&1 \
5 // RUN: | FileCheck %s --check-prefix=CHECK-ENABLED
8 // RUN: %clang --target=riscv32 -### %s 2>&1 -mno-default-build-attributes \
9 // RUN: | FileCheck %s --check-prefix=CHECK-DISABLED
10 // RUN: %clang --target=riscv64 -### %s 2>&1 -mno-default-build-attributes \
11 // RUN: | FileCheck %s --check-prefix=CHECK-DISABLED
12 // RUN: %clang --target=riscv32 -### %s 2>&1 -mdefault-build-attributes \
13 // RUN: | FileCheck %s --check-prefix=CHECK-ENABLED
[all …]
/llvm-project/llvm/utils/gn/secondary/clang/test/
H A DBUILD.gn1 import("//clang/lib/ARCMigrate/enable.gni")
2 import("//clang/lib/StaticAnalyzer/Frontend/enable.gni")
6 import("//llvm/utils/gn/build/libs/pthread/enable.gni")
7 import("//llvm/utils/gn/build/libs/zlib/enable.gni")
8 import("//llvm/utils/gn/build/libs/zstd/enable.gni")
9 import("//llvm/utils/gn/build/write_cmake_config.gni")
10 import("//llvm/utils/llvm-lit/lit_path_function.gni")
23 rebase_path(get_label_info("//clang", "target_out_dir"), dir),
24 "CLANG_SOURCE_DIR=" + rebase_path("//clang", dir),
33 # See comment for Windows solink in llvm/utils/gn/build/toolchai
[all...]
/llvm-project/clang/
H A DINSTALL.txt1 //===----------------------------------------------------------------------===//
2 // Clang Installation Instructions
3 //===----------------------------------------------------------------------===//
5 These instructions describe how to build and install Clang.
7 //===----------------------------------------------------------------------===//
9 //===----------------------------------------------------------------------===//
11 Clang is designed to be built as part of an LLVM build. Assuming that the LLVM
12 source code is located at $LLVM_SRC_ROOT, then the clang source code should be
15 $LLVM_SRC_ROOT/tools/clang
17 The directory is not required to be called clang, but doing so will allow the
[all …]
/llvm-project/clang/test/Modules/
H A Dpreprocess-build.cpp1 // RUN: %clang_cc1 -std=c++1z -fmodules %s -verify
3 #pragma clang module build baz
5 #pragma clang module endbuild // baz
7 #pragma clang module build foo
9 #pragma clang module contents
10 #pragma clang module begin foo.bar
12 // Can import baz here even though it was created in an outer build.
13 #pragma clang module import baz
15 #pragma clang module build bar
17 #pragma clang module contents
[all …]
/llvm-project/clang/cmake/caches/
H A DREADME.txt4 This directory contains CMake cache scripts that pre-populate the CMakeCache in
5 a build directory with commonly used settings.
9 cmake -G <build system>
10 -C <path to cache file>
11 [additional CMake options (i.e. -DCMAKE_INSTALL_PREFIX=<install path>)]
18 Apple-stage1
19 ------------
21 The Apple stage1 cache configures a two stage build similar to how Apple builds
22 the clang shipped with Xcode. The build files generated from this invocation has
23 a target named "stage2" which performs an LTO build of clang.
[all …]
/llvm-project/flang/
H A D.drone.star1 def clang(arch):
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 …clang-8 CXX=clang++-8 CXXFLAGS="-stdlib=libc++" LDFLAGS="-fuse-ld=lld" cmake -GNinja -DCMAKE_BUILD…
16 "mkdir build && cd build",
17 …clang-8 CXX=clang++-8 CXXFLAGS="-UNDEBUG -stdlib=libc++" LDFLAGS="-fuse-ld=lld" cmake -GNinja -DCM…
18 "ninja -j8",
19 "ctest --output-on-failure -j24",
[all …]

12345678910>>...42