/llvm-project/openmp/ |
H A D | README.rst | 5 and Clang need a more recent version which also applies for in-tree builds. For 15 - When calling CMake for the first time, all needed compiler options must be 20 - Example of configuring, building, reconfiguring, rebuilding: 22 .. code-block:: console 26 $ cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ .. # Initial configuration 30 $ cmake -DCMAKE_BUILD_TYPE=Debug .. # Second configuration 33 $ rm -rf * 34 $ cmake -DCMAKE_C_COMPILER=gcc -DCMAKE_CXX_COMPILER=g++ .. # Third configuration 37 - Notice in the example how the compiler definitions are only specified for an 39 - The file ``CMakeCache.txt`` which is created after the first call to CMake is [all …]
|
/llvm-project/clang/tools/clang-fuzzer/ |
H A D | README.txt | 1 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. 6 clang-fuzzer makes no attempt to generate valid C++ programs and is therefore 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 15 clang-proto-fuzzer is better at stressing deeper layers of Clang and LLVM. 20 Building clang-fuzzer [all …]
|
H A D | Dockerfile | 1 #===- llvm/tools/clang/tools/clang-fuzzer ---------------------------------===// 5 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 7 #===----------------------------------------------------------------------===// 8 # Produces an image that builds clang-proto-fuzzer 10 RUN apt-get update -y 11 RUN apt-get install -y autoconf automake libtool curl make g++ unzip wget git \ 12 binutils liblzma-dev libz-dev python-all cmake ninja-build subversion \ 13 pkg-config docbook2x 18 RUN wget -qO- https://github.com/google/protobuf/releases/download/v3.3.0/protobuf-cpp-3.3.0.tar.gz… 19 RUN cd protobuf-3.3.0 && ./autogen.sh && ./configure && make -j $(nproc) && make check -j $(nproc) … [all …]
|
/llvm-project/libc/docs/ |
H A D | full_cross_build.rst | 26 * **Standalone cross build** - Using this recipe one can build the libc using a 29 * **Bootstrap cross build** - In this recipe, one will build the ``clang`` 51 -------- [all...] |
H A D | overlay_mode.rst | 31 Building LLVM-libc as a standalone runtime 32 --------- [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 --- 36 compiler-rt. Note that compiler-rt is only needed to access libraries that 39 includig GNU and clang. But building compiler-rt requres using the clang 44 into a directory called llvm-project. The build will also 46 the built files), install (holds the installed files, and compiler-rt (holds 47 the result of building compiler-rt). [all …]
|
H A D | FortranLLVMTestSuite.md | 4 --- 6 --- 9 The [LLVM Test Suite](https://github.com/llvm/llvm-test-suite) is a 11 first-time users read through [LLVM Test Suite 15 ## Running the LLVM test-suite with Fortran 19 cmake -G "Ninja" -DCMAKE_C_COMPILER=<path to C compiler> \ 20 -DCMAKE_CXX_COMPILER=<path to C++ compiler> \ 21 -DCMAKE_Fortran_COMPILER=<path to Fortran compiler> \ 22 -DTEST_SUITE_COLLECT_CODE_SIZE:STRING=OFF \ 23 -DTEST_SUITE_SUBDIRS:STRING="Fortran" \ [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. 20 the compile-time performance gains are coming from, and verify that the speed-ups are 27 on how to obtain and build Clang in [Bootstrapping Clang-7 with PGO and LTO](#bootstrapping-clang-7-wit [all...] |
/llvm-project/llvm/docs/ |
H A D | HowToBuildWithPGO.rst | 2 How To Build Clang and LLVM with Profile-Guided Optimizations 8 PGO (Profile-Guided Optimization) allows your compiler to better optimize code 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 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 32 If you want to get the most out of PGO for a particular use-case (e.g. compiling 39 This script also supports a ``--dry-run`` option, which causes it to print 52 - runs all of Clang and LLVM's lit tests, and [all …]
|
/llvm-project/libc/docs/gpu/ |
H A D | building.rst | 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-compiling 23 support using the ``--target=<triple>`` flag. The following sections will 30 - [all...] |
/llvm-project/openmp/runtime/ |
H A D | README.txt | 9 should come with pre-built PDF documentation in doc/Reference.pdf. 26 In-tree build: 28 $ cd where-you-want-to-live 30 $ cd where-you-want-to-build 32 $ cmake path/to/llvm -DCMAKE_C_COMPILER=<C compiler> -DCMAKE_CXX_COMPILER=<C++ compiler> 35 Out-of-tree build: 37 $ cd where-you-want-to-live 39 $ cd where-you-want-to-live/openmp/runtime 41 $ cmake path/to/openmp -DCMAKE_C_COMPILER=<C compiler> -DCMAKE_CXX_COMPILER=<C++ compiler> 48 * IA-32 architecture [all …]
|
/llvm-project/mlir/test/Examples/standalone/ |
H A D | test.toy | 1 # RUN: "%cmake_exe" "%mlir_src_root/examples/standalone" -G "%cmake_generator" \ 2 # RUN: -DCMAKE_CXX_COMPILER=%host_cxx -DCMAKE_C_COMPILER=%host_cc \ 3 # RUN: -DLLVM_ENABLE_LIBCXX=%enable_libcxx -DMLIR_DIR=%mlir_cmake_dir \ 4 # RUN: -DLLVM_USE_LINKER=%llvm_use_linker \ 5 # RUN: -DPython3_EXECUTABLE=%python 6 # RUN: "%cmake_exe" --build . --target check-standalone | tee %t | FileCheck %s
|
/llvm-project/clang/cmake/modules/ |
H A D | ProtobufMutator.cmake | 8 set(PBM_LIB_PATH ${PBM_PATH}-build/src/libprotobuf-mutator.a) 9 set(PBM_FUZZ_LIB_PATH ${PBM_PATH}-build/src/libfuzzer/libprotobuf-mutator-libfuzzer.a) 13 GIT_REPOSITORY https://github.com/google/libprotobuf-mutator.git 15 CMAKE_ARGS -DCMAKE_BUILD_TYPE=${CMAKE_BUILD_TYPE} 16 CMAKE_CACHE_ARGS -DCMAKE_C_COMPILER:FILEPATH=${CMAKE_C_COMPILER} 17 -DCMAKE_CXX_COMPILER:FILEPATH=${CMAKE_CXX_COMPILER}
|
/llvm-project/compiler-rt/lib/sanitizer_common/symbolizer/scripts/ |
H A D | build_symbolizer.sh | 7 # Script compiles self-contained object file with symbolization code. 10 # libraries to symbolize code/data in-process. 14 # want to be doing "ld -r" followed by "objcopy -G" to create a relocatable 16 # present, see https://github.com/llvm/llvm-project/issues/30098. 18 set -x 19 set -e 20 set -u 23 SRC_DIR=$(readlink -f $SCRIPT_DIR/..) 25 if [[ $# -n [all...] |
/llvm-project/llvm/cmake/modules/ |
H A D | LLVMExternalProjectUtils.cmake | 12 string(JOIN "@" make_cmd "$(MAKE)" "-C" "${bin_dir}" "${target}") 14 set(${out_var} ${CMAKE_COMMAND} "-DLOCK_FILE_PATH=${stamp_dir}/cmake.lock" 15 "-DCOMMAND=${make_cmd}" 16 "-P" "${file_lock_script}" PARENT_SCOPE) 21 string(PREPEND tool_args "-- ") 24 set(${out_var} ${CMAKE_COMMAND} --build ${bin_dir} --targe [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/mlir/utils/clang-tidy/ |
H A D | README.md | 1 ### 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 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 \ 25 -DLLVM_TARGETS_TO_BUILD=Native \ [all …]
|
/llvm-project/libcxx/docs/ |
H A D | Modules.rst | 51 * ``LIBCXX_ENABLE_EXCEPTIONS`` [#note-no-windows]_ 57 .. [#note-no-windows] This configuration will probably not work on Windows 58 due to hard-coded compilation flags. 69 * The path to the compiler may not be a symlink, ``clang-scan-deps`` does 74 hard to solve and there is a work-around by first including all headers 75 `bug report <https://github.com/llvm/llvm-project/issues/61465>`__. 92 `bug report <https://github.com/llvm/llvm-project/issues/62943>`__. 118 .. code-block:: bash 120 $ git clone https://github.com/llvm/llvm-project.git 121 $ cd llvm-project [all …]
|
/llvm-project/clang/docs/ |
H A D | ThinLTO.rst | 13 runtime performance through whole-program analysis and cross-module 22 locations for later cross-module function importing. Fast and efficient 23 whole-program analysis is then performed on the combined summary index. 34 <http://blog.llvm.org/2016/06/thinlto-scalable-and-incremental-lto.html>`_. 43 ---------- 53 ------- 59 - **gold (via the gold-plugin)**: 63 - **ld64**: 65 - **lld**: 72 ----- [all …]
|
H A D | HowToSetupToolingForLLVM.rst | 7 of specific tools using this infrastructure (e.g. ``clang-check``). This 18 using a command line parameter ``-p`` or let Clang Tooling find this 31 .. code-block:: console 35 $ cmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON path/to/llvm/sources 38 ``-DCMAKE_C_COMPILER=/path/to/clang -DCMAKE_CXX_COMPILER=/path/to/clang++``. 46 .. code-block:: console 48 $ ln -s $PWD/compile_commands.json path/to/llvm/source/ 52 .. code-block:: console 54 $ make check-all 72 <https://docs.microsoft.com/en-us/cpp/build/building-on-the-command-line?view=msvc-170#path_and_env… [all …]
|
/llvm-project/mlir/examples/minimal-opt/ |
H A D | README.md | 6 - mlir-cat: This includes the Core IR, the builtin dialect, the textual 8 - mlir-minimal-opt: This adds all the tooling for an mlir-opt tool: the pass 10 - mlir-miminal-opt-canonicalize: This add the canonicalizer pass, which pulls in 14 using clang-14 on a X86 Ubuntu and [bloaty](https://github.com/google/bloaty). 17 | :------------------------------: | ------ | ------ | ------ | ------ | ------ | 18 | `mlir-cat` | 1024KB | 840KB | 885KB | 706KB | 657KB | 19 | `mlir-minimal-opt` | 1.62MB | 1.32MB | 1.36MB | 1.17MB | 1.07MB | 20 | `mlir-minimal-opt-canonicalize` | 1.83MB | 1.40MB | 1.45MB | 1.25MB | 1.14MB | 25 cmake ../llvm/ -G Ninja \ 26 -DCMAKE_BUILD_TYPE=RelWithDebInfo \ [all …]
|
/llvm-project/.github/workflows/ |
H A D | ci-post-commit-analyzer.yml | 1 name: Post-Commit Static Analyzer 9 - 'release/**' 11 - 'clang/**' 12 - 'llvm/**' 13 - '.github/workflows/ci-post-commit-analyzer.yml' 16 - opened 17 - synchronize 18 - reopened 19 - closed 21 - '.github/workflows/ci-post-commit-analyzer.yml' [all …]
|
/llvm-project/libcxx/benchmarks/ |
H A D | CMakeLists.txt |
|
/llvm-project/libc/config/windows/ |
H A D | README.md | 21 [Ninja](https://github.com/ninja-build/ninja/releases). (Optional, included 34 [Git](https://git-scm.com/download/win) for Windows. Check out the LLVM 38 git clone https://github.com/llvm/llvm-project.git 54 mkdir libc-build 55 cd libc-build 62 …-G Ninja ../llvm-project/llvm -DCMAKE_C_COMPILER=C:/src/clang-build/bin/clang-cl.exe -DCMAKE_CXX_C… 71 -DLLVM_LIBC_MPFR_INSTALL_PATH=<path/mpfr/install/dir>
|
/llvm-project/libcxx/ |
H A D | appveyor.yml |
|