/llvm-project/libcxx/docs/ |
H A D | TestingLibcxx.rst | 15 The primary way to run the libc++ tests is by using ``make check-cxx``. 27 ----- 30 running ``llvm-lit`` on a specified test or directory. If you're unsure 32 ``cxx-test-depends`` target. For example: 34 .. code-bloc [all...] |
H A D | Contributing.rst | 11 If you plan on contributing to libc++, it can be useful to join the ``#libcxx`` channel 14 Looking for pre-existing pull requests 19 filtering pull requests `tagged with libc++ <https://github.com/llvm/llvm-project/pulls?q=is%3Apr+is%3Aopen+label%3Alibc%2B%2B>`__. 23 RFCs for significant user-affecting changes 27 please consider creating a RFC on the `libc++ forum <https://discourse.llvm.org/c/runtimes/libcxx>`_. 49 ----- [all...] |
H A D | BuildingLibcxx.rst |
|
/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 | libcxx-build-and-test.yaml | 1 # This file defines pre-commit CI for libc++, libc++abi, and libunwind (on Github). 4 # when a job fails early in the pipeline. This is why the jobs are marked as `continue-on-error: false`. 7 # Stages 1 & 2 are meant to be "smoke tests", and are meant to catch most build/test failures quickly and without using 11 # Therefore, we "fail-fast" for any failures during stages 1 & 2, meaning any job failing cancels all other running jobs, 13 # However, stage 3 does not fail fast, as it's more likely that any one job failing is a flake or a configuration-specific 15 name: Build and Test libc++ 19 - 'libcxx/**' 20 - 'libcxxab [all...] |
/llvm-project/libcxx/utils/ci/ |
H A D | run-buildbot | 2 # ===---------- [all...] |
H A D | Dockerfile | 1 # ===---------- [all...] |
H A D | oss-fuzz.sh | 1 #!/bin/bash -eu 4 # This script runs the continuous fuzzing tests on OSS-Fuzz. 8 …CXXFLAGS="${CXXFLAGS} -fsanitize=unsigned-integer-overflow -fsanitize-trap=unsigned-integer-overfl… 11 BUILD=cxx_build_dir 15 mkdir ${BUILD} 16 cmake -S ${MONOREPO_ROOT}/runtimes -B ${BUILD} \ 17 -DLLVM_ENABLE_RUNTIMES="libcxx;libcxxabi;libunwind" \ 18 -DCMAKE_BUILD_TYPE=RelWithDebInfo \ 19 -DCMAKE_INSTALL_PREFIX="${INSTALL}" 20 cmake --build ${BUILD} --target install-cxx-headers [all …]
|
H A D | apple-install-libcxx.sh | 2 # ===---------- [all...] |
H A D | macos-ci-setup |
|
H A D | docker-compose.yml | 1 x-versions: &compiler_versions 6 actions-builder: 7 image: ghcr.io/llvm/libcxx-linux-builder:${TAG} 8 build: 11 target: actions-builder 13 BASE_IMAGE: ghcr.io/actions/actions-runner:2.319.1 16 android-buildkite-builde [all...] |
H A D | buildkite-pipeline.yml | 1 # ===---------- [all...] |
H A D | run-buildbot-container | 3 # This script starts a shell in a container running the libc++ build bot Docker 7 # Once you're inside the shell, you can run the various build jobs with the 8 # `run-buildbot` script. 13 # is useful for editing files on the host machine and re-running the build bot 20 # --user $(id -u):$(id -g) 22 set - [all...] |
/llvm-project/libcxx/utils/ |
H A D | libcxx-lit | 3 set -e 9 ${PROGNAME} [-h|--help] [-b|--bootstrap] <build-directory> [lit options...] tests... 11 Shortcut to build th [all...] |
/llvm-project/lldb/test/ |
H A D | CMakeLists.txt | 14 # Lit uses psutil to do per-test timeouts. 35 # In order to run check-lldb-* we need the correct map_config directives in 36 # llvm-lit. Because this is a standalone build, LLVM doesn't know about LLDB, 37 # and the lldb mappings are missing. We build our own llvm-lit, and tell LLVM 38 # to use the llvm-lit in the lldb build directory. 39 if (EXISTS ${LLVM_MAIN_SRC_DIR}/utils/llvm-li [all...] |
/llvm-project/llvm/utils/gn/secondary/clang/tools/driver/ |
H A D | BUILD.gn | 1 import("//llvm/utils/gn/build/driver_executable.gni") 2 import("//llvm/utils/gn/build/symlink_or_copy.gni") 3 import("//llvm/utils/gn/build/write_cmake_config.gni") 13 "clang-cl", 14 "clang-cl", 17 "clang-cpp", 18 "clang-cpp", 29 # //:clang depends on this symlink target, see comment in //BUILD.gn. 51 configs += [ "//llvm/utils/gn/build:clang_code" ] 60 "//clang/tools/clang-linke [all...] |
/llvm-project/llvm/utils/gn/secondary/libcxx/src/ |
H A D | BUILD.gn | 2 import("//libcxx/config.gni") 3 import("//llvm/utils/gn/build/symlink_or_copy.gni") 6 # Build libc++ with definitions for operator new/delete. 9 # Build libc++ as a shared library. 12 # Build libc++ as a static library. 15 # Build filesystem as part of libc++. 18 # Build libc++experimental.a. 21 # Use compiler-rt builtins. 40 "-Wall", 41 "-Wextr [all...] |
/llvm-project/llvm/utils/gn/secondary/libcxxabi/src/ |
H A D | BUILD.gn | 7 # Build libc++abi with definitions for operator new/delete. 10 # Build libcxxabi as a shared library. 13 # Build libcxxabi as a static library. 66 "//libcxx/src", 69 "-std=c++23", 70 "-nostdinc++", 86 cflags = [ "-fPIC" ] 87 ldflags = [ "-nostdlib++" ] 96 "//compiler-rt/lib/builtins", 97 "//libcxx/include", [all …]
|
/llvm-project/libcxx/test/libcxx/ |
H A D | transitive_includes.gen.py | 1 # ===---------- [all...] |
/llvm-project/compiler-rt/ |
H A D | CMakeLists.txt | 1 # CMake build for CompilerRT. 3 # An important constraint of the build is that it only produces libraries 7 set(LLVM_SUBPROJECT_TITLE "Compiler-RT") 20 # Check if compiler-rt is built as a standalone project. 27 # Add path for custom compiler-rt modules. 42 include(base-config-ix) 49 # Check if we can compile with --no-defaul [all...] |
/llvm-project/clang/cmake/caches/ |
H A D | CrossWinToARMLinux.cmake | 3 # Set up a CMakeCache for a cross Windows to ARM Linux toolchain build. 5 # This cache file can be used to build a cross toolchain to ARM Linux 8 # NOTE: the build requires a development ARM Linux root filesystem to use 11 # The build generates a proper clang configuration file with stored 12 # --sysroot argument for specified target triple. Also it is possible 14 # -DCLANG_CONFIG_FILE_USER_DIR=<full-path-to-clan [all...] |
/llvm-project/lldb/packages/Python/lldbsuite/test/ |
H A D | dotest_args.py | 13 description="description", prefix_chars="+-", add_help=False 25 "-h", 26 "--help", 29 help="Print this help message and exit. Add '-v' for more detailed help.", 35 "-A", 36 "--arch", 44 "-C", 45 "--compiler", 49 …"""Specify the compiler(s) used to build the inferior executables. The compiler path can be an exe… 53 "--sysroot", [all …]
|
/llvm-project/libc/docs/ |
H A D | full_host_build.rst | 4 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/lldb/test/API/ |
H A D | lit.cfg.py | 1 # -*- Python -*- 15 config.name = "lldb-api" 41 subprocess.check_output([config.cmake_cxx_compiler, "-print-resource-dir"]) 42 .decode("utf-8") 69 copied_python = os.path.join(sys.prefix, "bin", "copied-pytho [all...] |
/llvm-project/llvm/utils/release/ |
H A D | build-docs.sh | 2 #===-- build-docs.sh - Tag the LLVM release candidates ---------------------===# 6 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception 8 #===------------------------------------------------------------------------===# 10 # Build documentation for LLVM releases. 14 # * dnf install doxygen texlive-epstopdf ghostscript \ 15 # ninja-build gcc-c++ 16 # * pip install --user -r ./llvm/docs/requirements.txt 18 # * apt-get install doxygen \ 19 # ninja-build graphviz texlive-font-utils 20 # * pip install --user -r ./llvm/docs/requirements.txt [all …]
|