| /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
18 target system which is not the same as the system on which the libc is being
22 There are two main recipes to cross build the full libc
[all...] |
| 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
18 the same system on which the libc is being built. First, we will explain how to
19 build for developing LLVM-lib
[all...] |
| H A D | overlay_mode.rst | 11 One can choose to use LLVM's libc in the overlay mode. In this mode, the link
14 libc. The user programs also have to use header files from the system libc.
20 Building the libc in the overlay mode
23 There are two different ways in which the libc can be built for use in the
24 overlay mode. In both the ways, we build a static archive named
26 it clear that it is not the system libc, which is typically named ``libc.a``.
27 Also, if users choose to mix more than one libc with the system libc, the
[all...] |
| H A D | build_and_test.rst | 4 Building and Testing the libc
7 Build modes
10 The libc can be built and tested in two different modes:
12 #. **The overlay mode** - In this mode, one uses the static archive from LLVM's
13 libc along with the system libc. See :ref:`overlay_mode` for more details
14 on building and using the libc in this mode. You can only run the libc
17 .. code-block:: sh
19 $> ninja check-lib
[all...] |
| /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
35 The GPU uses the same testing infrastructure as the other supported ``libc``
47 --------------
57 .. code-block:: c++
76 --------------
[all …]
|
| /llvm-project/libcxx/docs/ |
| H A D | BuildingLibcxx.rst | |
| H A D | Contributing.rst | 4 Contributing to libc++
7 This file contains information useful when contributing to libc++. If this is your first time contributing,
11 If you plan on contributing to libc++, it can be useful to join the ``#libcxx`` channel
14 Looking for pre-existing pull requests
17 Before you start working on any feature, please take a look at the open libc++ pull
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>`_.
35 Every change in libc
[all...] |
| H A D | TestingLibcxx.rst | 4 Testing libc++
13 libc++ uses LIT to configure and run its tests.
15 The primary way to run the libc++ tests is by using ``make check-cxx``.
17 However since libc++ can be used in any number of possible
20 test libc++.
27 ----
[all...] |
| H A D | Modules.rst | 4 Modules in libc++
7 .. warning:: Modules are an experimental feature. It has additional build
8 requirements and not all libc++ configurations are supported yet.
13 This page contains information regarding C++23 module support in libc++.
29 build and use the ``.pcm`` files. It is expected this will be done by build
30 systems in the future. To aid early adaptor and build system vendors libc++
35 on the availability of build systems with proper module support.
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.
[all …]
|
| /llvm-project/libc/examples/ |
| H A D | README.md | 4 up their own projects to use LLVM's libc, either as an overlay or as the only
5 libc in their projects. See the
6 [the usage mode document](https://libc.llvm.org/usage_modes.html) for more
7 information about the different modes in which one can build and use the libc.
12 build set up. To build an example, create a directory named `build` in the
17 mkdir build
18 cd build
21 Each example can be built to use the libc in either
22 [the overlay mode](https://libc.llvm.org/overlay_mode.html) or the
23 [full build mode](https://libc.llvm.org/fullbuild_mode.html). The CMake
[all …]
|
| /llvm-project/libc/config/windows/ |
| H A D | README.md | 1 # Building and Testing LLVM libc on Windows
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
45 ## Building LLVM libc
48 libc, and finally, build and test the libc.
[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
4 implementation to LLVM libc. To add a new function, apart from the actual
14 - Add entry points `libc.src.math.func` to the following files:
16 libc/config/linux/<arch>/entrypoints.txt
17 libc/config/windows/entrypoints.txt
19 - Add function specs to the file:
21 libc/include/math.yaml
29 - Ad
[all...] |
| /llvm-project/llvm/docs/ |
| H A D | HowToBuildWindowsItaniumPrograms.rst | 2 How to build Windows Itanium applications.
17 * libc++.
18 * libc++-abi.
25 Note: compiler-rt is not used. This functionality is supplied by the MS VCRT.
31 * Clang with support for the windows-itanium triple.
32 * COFF LLD with support for the -autoimport switch.
37 SJLJ exceptions, "-fsjlj-exceptions", are the only currently supported model.
39 link.exe (the MS linker) is unsuitable as it doesn't support auto-importin
[all...] |
| /llvm-project/libcxxabi/ |
| H A D | CMakeLists.txt | 1 # See www/CMake.html for instructions on how to build libcxxabi with CMake.
8 set(LLVM_SUBPROJECT_TITLE "libc++abi")
21 set(CMAKE_FOLDER "libc++")
26 "Specify path to libc++ source.")
30 # Require out of source build.
33 "${PROJECT_NAME} requires an out of source build. Please create a separate
34 build directory and run 'cmake /path/to/${PROJECT_NAME} [options]' there."
38 message(FATAL_ERROR "Libc++abi can't be built for MSVC targets, and doing so is pointless anyway because such "
39 "targets must use the MS C++ ABI, and libc++abi provides the Itanium C++ ABI.")
51 When disabled, libc
[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...] |
| /llvm-project/libc/cmake/modules/ |
| H A D | LLVMLibCArchitectures.cmake | 1 # ----------
[all...] |
| /llvm-project/libc/ |
| H A D | CMakeLists.txt | 2 set(LLVM_SUBPROJECT_TITLE "libc")
5 message(FATAL_ERROR "Builds rooted in the libc directory are not supported. "
7 "Please see the documentation at https://libc.llvm.org/usage_modes.html for more info.")
25 # `llvm-project/llvm/CMakeLists.txt` adds the following directive
34 add_definitions("-D_DEBUG")
42 # The top-level source directory.
44 # The top-level directory in which libc is being built.
47 set(LIBC_ENABLE_USE_BY_CLANG OFF CACHE BOOL "Whether or not to place libc in a build director
[all...] |
| /llvm-project/libcxx/ |
| H A D | CMakeLists.txt | 5 set(LLVM_SUBPROJECT_TITLE "libc++")
18 set(CMAKE_FOLDER "libc++")
26 # Require out of source build.
29 "${PROJECT_NAME} requires an out of source build. Please create a separate
30 build directory and run 'cmake /path/to/${PROJECT_NAME} [options]' there."
33 message(STATUS "Configuring for clang-cl")
47 # Basic options ----
[all...] |
| /llvm-project/lldb/test/API/commands/expression/import-std-module/module-build-errors/ |
| H A D | TestStdModuleBuildErrors.py | 2 Tests that the import-std-module=fallback setting is only showing the error
4 This is supposed to prevent that a broken libc++ module renders failing
6 module build errors.
16 # We only emulate a fake libc++ in this test and don't use the real libc++,
17 # but we still add the libc++ category so that this test is only run in
18 # test configurations where libc++ is actually supposed to be tested.
19 @add_test_categories(["libc++"])
23 self.build()
27 # Set the sysroot this test is using to provide a custom libc++.
29 "platform select --sysroot '" + sysroot + "' host", CURRENT_EXECUTABLE_SET
[all …]
|
| /llvm-project/llvm/utils/gn/secondary/libcxx/src/ |
| H A D | BUILD.gn | 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 lib
[all...] |
| /llvm-project/libcxx/utils/ci/ |
| H A D | apple-install-libcxx.sh | 2 # ===----------
[all...] |
| H A D | run-buildbot | 2 # ===----------
[all...] |
| /llvm-project/lldb/test/API/commands/expression/import-std-module/missing-module-sources/ |
| H A D | TestStdModuleSourcesMissing.py | 13 # We only emulate a fake libc++ in this test and don't use the real libc++,
14 # but we still add the libc++ category so that this test is only run in
15 # test configurations where libc++ is actually supposed to be tested.
16 @add_test_categories(["libc++"])
26 # Build the binary with the copied sources.
27 self.build()
31 # Set the sysroot where our dummy libc++ used to exist. Just to make
34 self.runCmd("platform select --sysroot '" + target_sysroot + "' host")
43 self.runCmd("settings set target.import-std-module true")
49 # Check that there is no confusing error about failing to build the
[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…
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",
20 "ninja check-all",
[all …]
|