| /llvm-project/llvm/test/MC/MachO/AArch64/ |
| H A D | arm-darwin-version-min-load-command.s | 1 …llvm-mc -triple arm64-apple-macos10.10.2 %s -filetype=obj -o - | llvm-objdump --macho --private-he…
2 …llvm-mc -triple arm64e-apple-macos10.10 %s -filetype=obj -o - | llvm-objdump --macho --private-hea…
3 …: llvm-mc -triple arm64-apple-macos11 %s -filetype=obj -o - | llvm-objdump --macho --private-heade…
4 … llvm-mc -triple arm64-apple-macos11.1 %s -filetype=obj -o - | llvm-objdump --macho --private-head…
5 …llvm-mc -triple arm64-apple-ios13.0-macabi %s -filetype=obj -o - | llvm-objdump --macho --private-…
6 …llvm-mc -triple arm64e-apple-ios13.0-macabi %s -filetype=obj -o - | llvm-objdump --macho --private…
7 …llvm-mc -triple arm64-apple-ios14.1-macabi %s -filetype=obj -o - | llvm-objdump --macho --private-…
9 …: llvm-mc -triple arm64e-apple-ios10.3 %s -filetype=obj -o - | llvm-objdump --macho --private-head…
10 …N: llvm-mc -triple arm64e-apple-ios13 %s -filetype=obj -o - | llvm-objdump --macho --private-heade…
11 …: llvm-mc -triple arm64e-apple-ios14.1 %s -filetype=obj -o - | llvm-objdump --macho --private-head…
[all …]
|
| /llvm-project/llvm/test/MC/MachO/ |
| H A D | darwin-version-min-load-command.s | 1 // RUN: llvm-mc -triple x86_64-apple-macosx10.10.0 %s -filetype=obj -o - | llvm-objdump --macho --p…
2 …/ RUN: llvm-mc -triple x86_64-apple-ios8.0.0 %s -filetype=obj -o - | llvm-objdump --macho --privat…
3 // RUN: llvm-mc -triple x86_64-apple-darwin %s -filetype=obj -o - | llvm-objdump --macho --private-…
4 …UN: llvm-mc -triple x86_64-apple-ios13.0-macabi %s -filetype=obj -o - | llvm-objdump --macho --pri…
6 …N: llvm-mc -triple x86_64-apple-macos10.14 %s -filetype=obj -o - | llvm-objdump --macho --private-…
7 …RUN: llvm-mc -triple x86_64-apple-ios12 %s -filetype=obj -o - | llvm-objdump --macho --private-hea…
8 …RUN: llvm-mc -triple x86_64-apple-tvos12 %s -filetype=obj -o - | llvm-objdump --macho --private-he…
9 …UN: llvm-mc -triple x86_64-apple-watchos5 %s -filetype=obj -o - | llvm-objdump --macho --private-h…
10 …llvm-mc -triple x86_64-apple-ios12-simulator %s -filetype=obj -o - | llvm-objdump --macho --privat…
11 …llvm-mc -triple x86_64-apple-tvos12-simulator %s -filetype=obj -o - | llvm-objdump --macho --priva…
[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 | 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-lib
[all...] |
| /llvm-project/.github/workflows/ |
| 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 | docs.yml | 1 # LLVM Documentation CI
2 # Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
3 # See https://llvm.org/LICENSE.txt for license information.
4 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
6 name: "Test documentation build"
[all...] |
| /llvm-project/flang/docs/ |
| H A D | GettingStarted.md | 1 <!--===- docs/GettingStarted.md
3 Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
4 See https://llvm.org/LICENSE.txt for license information.
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
[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
20 The LLVM C library currently supports two GPU targets. This is either
21 ``nvptx64-nvidia-cuda`` for NVIDIA GPUs or ``amdgcn-am
[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
13 (GNU make, Visual Studio, etc.) for building LLVM.
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.
[all …]
|
| H A D | CMake.rst | 2 Building LLVM with CMake
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
13 (GNU make, Visual Studio, etc.) for building LLVM.
19 If you are really anxious about getting a functional LLVM build, go to the
22 `Options and variables`_ section is a reference for customizing your build
[all...] |
| H A D | GettingStarted.rst | 2 Getting Started with the LLVM System
11 Welcome to the LLVM project!
13 The LLVM project has multiple components. The core of the project is
14 itself called "LLVM". This contains all of the tools, libraries, and header
19 C-like languages use the `Clang <https://clang.llvm.org/>`_ front end. This
20 component compiles C, C++, Objective C, and Objective C++ code into LLVM bitcode
21 -- and from there into object files, using LLVM
[all...] |
| H A D | HowToAddABuilder.rst | 2 How To Add Your Build Configuration To LLVM Buildbot Infrastructure
8 This document contains information about adding a build configuration and
9 buildbot worker to the LLVM Buildbot Infrastructure.
22 * The main buildmaster at `<https://lab.llvm.org/buildbot>`_. All builders
24 the build.
25 * The staging buildmaster at `<https://lab.llvm.org/staging>`_. All builders
26 attached to this machine will be completely silent by default when the build
28 commits from the llvm-zor
[all...] |
| 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
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 …]
|
| /llvm-project/llvm/utils/gn/ |
| H A D | README.rst | 2 Building LLVM with GN
13 *Warning* The GN build is experimental and best-effort. It might not work,
15 necessary. LLVM's official build system is CMake, if in doubt use that.
16 If you add files, you're expected to update the CMake build but you don't need
17 to update GN build files. Reviewers should not ask authors to update GN build
18 files. Keeping the GN build files up-to-date is on the people who use the GN
19 build.
23 which then shell out to ninja for the actual build.
25 The main motivation behind the GN build is that some people find it more
26 convenient for day-to-day hacking on LLVM than CMake. Distribution, building
[all …]
|
| /llvm-project/lld/test/ELF/ |
| H A D | build-id.s | 3 # RUN: llvm-mc -filetype=obj -triple=x86_64-unknown-linux %s -o %t
5 # RUN: ld.lld --build-id %t -o %t2
6 # RUN: llvm-readobj -S %t2 | FileCheck -check-prefix=ALIGN %s
8 # RUN: ld.lld --build-id %t -o %t2
9 # RUN: llvm-objdump -s %t2 | FileCheck --check-prefix=SHA1 %s
10 # RUN: ld.lld --build-id %t -o %t2 --threads=1
11 # RUN: llvm-objdump -s %t2 | FileCheck --check-prefix=SHA1 %s
13 # RUN: ld.lld --build-id=fast %t -o %t2
14 # RUN: llvm-objdump -s %t2 | FileCheck --check-prefix=FAST %s
16 # RUN: ld.lld --build-id=md5 %t -o %t2
[all …]
|
| /llvm-project/llvm/test/ThinLTO/X86/ |
| H A D | selective-save-temps.ll | 1 ; UNSUPPORTED: system-windows
5 ; RUN: rm -rf %t && mkdir %t && cd %t
7 ;; Copy IR from import-constant.ll since it generates all the temps
8 ; RUN: opt -thinlto-bc %s -o 1.bc
9 ; RUN: opt -thinlto-bc %p/Inputs/import-constant.ll -o 2.bc
11 ;; Create the .all dir with save-temps saving everything, this will be used to compare
12 ;; with the output from individualized save-temps later
13 ; RUN: mkdir all all2 build subset subset2
14 ; RUN: llvm-lto2 run 1.bc 2.bc -o all/a.out \
15 ; RUN: -import-constants-with-refs -r=1.bc,main,plx -r=1.bc,_Z6getObjv,l \
[all …]
|
| /llvm-project/llvm/utils/gn/secondary/compiler-rt/lib/ubsan/ |
| H A D | BUILD.gn | 1 import("//compiler-rt/gen_version_script.gni")
2 import("//compiler-rt/target.gni")
28 configs -= [ "//llvm/utils/gn/build:llvm_code" ]
29 configs += [ "//llvm/utils/gn/build:crt_code" ]
31 "//compiler-rt/lib/interception:sources",
32 "//compiler-rt/lib/sanitizer_common:sources",
54 configs -
[all...] |
| /llvm-project/llvm/test/DebugInfo/PDB/Native/ |
| H A D | pdb-native-compilands.test | 2 ; RUN: llvm-pdbutil pretty -native -compilands %p/../Inputs/empty.pdb \
3 ; RUN: | FileCheck -check-prefix=EMPTY %s
4 ; RUN: llvm-pdbutil pretty -native -compilands %p/../Inputs/big-read.pdb \
5 ; RUN: | FileCheck -check-prefix=BIGREAD %s
6 ; RUN: llvm-pdbutil diadump -native -compilands %p/../Inputs/empty.pdb \
7 ; RUN: | FileCheck -check-prefix=DUMP %s
10 ; `-native` option produces identical output. The paths output will have
11 ; backslashes even on non-Windows platforms because they are from PDBs built
13 ; machine-specific.
15 EMPTY:---COMPILANDS---
[all …]
|
| /llvm-project/utils/bazel/ |
| H A D | README.md | 3 *Warning* The Bazel build is experimental and best-effort, supported in line
5 [LLVM's peripheral support tier](https://llvm.org/docs/SupportPolicy.html).
6 LLVM's official build system is CMake. If in doubt use that. If you make changes
7 to LLVM, you're expected to update the CMake build but you don't need to update
8 Bazel build files. Reviewers should not ask authors to update Bazel build file
[all...] |
| /llvm-project/lldb/docs/resources/ |
| H A D | build.rst | 5 ----------
[all...] |
| /llvm-project/libunwind/docs/ |
| H A D | BuildingLibunwind.rst | 15 On Mac OS, the easiest way to get this library is to link with -lSystem.
16 However if you want to build tip-of-trunk from here (getting the bleeding
19 The basic steps needed to build libunwind are:
21 #. Checkout LLVM, libunwind, and related projects:
23 * ``cd where-you-want-llvm
[all...] |
| /llvm-project/libc/AOR_v20.02/string/ |
| H A D | Dir.mk | 1 # Makefile fragment - requires GNU make
3 # Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
4 # See https://llvm.org/LICENSE.txt for license information.
5 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
8 B := build/string
11 all-string check-string install-string clean-string:
16 string-lib-srcs := $(wildcard $(S)/$(ARCH)/*.[cS])
17 string-test-srcs := $(wildcard $(S)/test/*.c)
19 string-includes := $(patsubst $(S)/%,build/%,$(wildcard $(S)/include/*.h))
21 string-libs := \
[all …]
|
| /llvm-project/mlir/examples/standalone/ |
| H A D | README.md | 1 # An out-of-tree MLIR dialect
3 This is an example of an out-of-tree [MLIR](https://mlir.llvm.org/) dialect along with a standalone…
5 ## Building - Component Build
7 This setup assumes that you have built LLVM and MLIR in `$BUILD_DIR` and installed them to `$PREFIX…
9 mkdir build && cd build
10 cmake -G Ninja .. -DMLIR_DIR=$PREFIX/lib/cmake/mlir -DLLVM_EXTERNAL_LIT=$BUILD_DIR/bin/llvm-lit
11 cmake --build . --target check-standalone
13 To build the documentation from the TableGen description of the dialect operations, run
15 cmake --build . --target mlir-doc
17 **Note**: Make sure to pass `-DLLVM_INSTALL_UTILS=ON` when building LLVM with CMake in order to ins…
[all …]
|
| /llvm-project/clang/docs/ |
| H A D | HowToSetupToolingForLLVM.rst | 2 How To Setup Clang Tooling For LLVM
7 of specific tools using this infrastructure (e.g. ``clang-check``). This
9 the LLVM source code.
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
28 First, you need to generate Makefiles for LLVM with CMake. You need to
29 make a build directory and run CMake from it:
[all …]
|
| /llvm-project/libcxx/docs/ |
| H A D | Modules.rst | 7 .. warning:: Modules are an experimental feature. It has additional build
16 * `Clang specific modules <https://clang.llvm.org/docs/Modules.html>`_
17 * `C++ modules <https://clang.llvm.org/docs/StandardCPlusPlusModules.html>`_
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.
63 * There is no official build system support, libc++ has experimental CMake support
[all …]
|