Home
last modified time | relevance | path

Searched full:build (Results 1 – 25 of 4389) sorted by relevance

12345678910>>...176

/llvm-project/polly/lib/External/isl/
H A Disl_ast_build.c33 __isl_keep isl_ast_build *build, __isl_take isl_set *set) in isl_ast_build_map_to_iterator() argument
40 if (!build) in isl_ast_build_map_to_iterator()
43 map = isl_map_equate(map, isl_dim_in, build->depth, isl_dim_out, 0); in isl_ast_build_map_to_iterator()
44 map = isl_map_eliminate(map, isl_dim_in, build->depth, 1); in isl_ast_build_map_to_iterator()
56 __isl_take isl_ast_build *build, __isl_take isl_space *space) in isl_ast_build_init_derived() argument
62 build = isl_ast_build_cow(build); in isl_ast_build_init_derived()
63 if (!build || !build->domain) in isl_ast_build_init_derived()
66 ctx = isl_ast_build_get_ctx(build); in isl_ast_build_init_derived()
73 isl_vec_free(build->strides); in isl_ast_build_init_derived()
74 build->strides = strides; in isl_ast_build_init_derived()
[all …]
H A Disl_ast_build_private.h94 * "options" contains the AST build options in case we are generating
170 __isl_keep isl_ast_build *build, void *user);
182 __isl_keep isl_ast_build *build, void *user);
190 __isl_take isl_ast_build *build, void *user);
203 __isl_take isl_ast_build *build);
205 __isl_take isl_ast_build *build);
206 isl_size isl_ast_build_get_depth(__isl_keep isl_ast_build *build);
207 isl_size isl_ast_build_dim(__isl_keep isl_ast_build *build,
210 __isl_keep isl_ast_build *build, int internal);
212 __isl_take isl_ast_build *build, __isl_take isl_space *model);
[all …]
H A Disl_ast_codegen.c53 * "build" is the input build.
57 isl_ast_build *build; member
64 __isl_take isl_ast_build *build);
66 __isl_take isl_union_map *executed, __isl_take isl_ast_build *build,
92 isl_ast_build *build; in generate_non_single_valued() local
95 build = isl_ast_build_copy(data->build); in generate_non_single_valued()
99 build = isl_ast_build_set_single_valued(build, 1); in generate_non_single_valued()
101 list = generate_code(isl_union_map_from_map(executed), build, 1); in generate_non_single_valued()
109 * after recording the current inverse schedule in the build.
112 __isl_keep isl_map *executed, __isl_keep isl_ast_build *build) in at_each_domain() argument
[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** - In this recipe, one will build th
[all...]
/llvm-project/llvm/test/MC/MachO/
H A Ddarwin-version-min-load-command.s6 …obj -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-MACOS
7 …e=obj -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-IOS
8 …=obj -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-TVOS
9 …j -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-WATCHOS
10 …bj -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-IOSSIM
11 …j -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-TVOSSIM
12 …o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-WATCHOSSIM
61 // CHECK-BUILD-MACOS: cmd LC_BUILD_VERSION
62 // CHECK-BUILD-MACOS-NEXT: cmdsize 24
63 // CHECK-BUILD-MACOS-NEXT: platform macos
[all …]
/llvm-project/clang/docs/analyzer/user-docs/
H A DCommandLineUsage.rst1 Command Line Usage: scan-build and CodeChecker
5 CodeChecker and scan-build are two CLI tools for using CSA on multiple files (translation units).
10 Comparison of CodeChecker and scan-build
26 - Generally much more feature-rich than scan-build.
32 scan-build
35 **scan-build** is a command line utility that enables a user to run the static analyzer over their codebase as part of performing a regular build (from the command line).
40 During a project build, as source files are compiled they are also analyzed in tandem by the static analyzer.
42 Upon completion of the build, results are then presented to the user within a web browser.
44 Will it work with any build syste
[all...]
/llvm-project/llvm/test/MC/MachO/AArch64/
H A Darm-darwin-version-min-load-command.s1 … - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-MACOS-ARM64
2 … - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-MACOS-ARM64
3 … - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-MACOS-ARM64
4 … | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-MACOS-ARM64_1
9 …o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-IOS-ARM64E
10 …o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-IOS-ARM64E
11 … - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-IOS-ARM64E3
13 …j -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-IOSSIM2
14 …j -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-IOSSIM2
15 …j -o - | llvm-objdump --macho --private-headers - | FileCheck %s --check-prefix=CHECK-BUILD-IOSSIM2
[all …]
/llvm-project/libc/AOR_v20.02/string/
H A DDir.mk8 B := build/string
19 string-includes := $(patsubst $(S)/%,build/%,$(wildcard $(S)/include/*.h))
22 build/lib/libstringlib.so \
23 build/lib/libstringlib.a \
26 build/bin/test/memcpy \
27 build/bin/test/memmove \
28 build/bin/test/memset \
29 build/bin/test/memchr \
30 build/bin/test/memcmp \
31 build/bin/test/strcpy \
[all …]
/llvm-project/llvm/test/ThinLTO/X86/
H A Dselective-save-temps.ll13 ; RUN: mkdir all all2 build subset subset2
30 ; RUN: llvm-lto2 run 1.bc 2.bc -o build/a.out \
34 ; RUN: cmp all/a.out.1 build/a.out.1 && rm -f build/a.out.1
35 ; RUN: cmp all/a.out.2 build/a.out.2 && rm -f build/a.out.2
36 ; RUN: cp build/*.0.preopt.* subset2
37 ; RUN: mv build/*.0.preopt.* all2
38 ; RUN: ls build | count 0
42 ; RUN: llvm-lto2 run 1.bc 2.bc -o build/a.out \
46 ; RUN: cmp all/a.out.1 build/a.out.1 && rm -f build/a.out.1
47 ; RUN: cmp all/a.out.2 build/a.out.2 && rm -f build/a.out.2
[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
30 $ scan-build <your build command>
34 $ intercept-build <your build command>
39 $ analyze-build
49 $ intercept-build <your build command>
54 $ analyze-build --ctu
62 $ analyze-build --ctu-collect-only
[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>`
24 describe how to build the GPU support specifically.
29 Standard runtimes build
32 The simplest way to build the GPU libc is to use the existing LLVM runtimes
34 compiler and using it to build the C library. The following CMake invocation
35 will instruct it to build the ``libc`` runtime targeting both AMD and NVIDIA
42 $> mkdir build
43 $> cd build
[all...]
/llvm-project/flang/docs/
H A DGettingStarted.md18 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
30 All of the examples below use GCC as the C/C++ compilers and ninja as the build
38 tests. You can use several different C++ compilers for most of the build,
40 compiler built in the initial part of the build.
44 into a directory called llvm-project. The build will also
45 create subdirectories under the root directory called build (holds most of
[all …]
/llvm-project/.github/workflows/
H A Drelease-binaries.yml16 description: "Runner to use for the build"
37 description: "Runner to use for the build"
51 name: Prepare to build binaries
60 build-flang: ${{ steps.vars.outputs.build-flang }}
64 build-runs-on: ${{ steps.vars.outputs.build-runs-on }}
65 test-runs-on: ${{ steps.vars.outputs.build-runs-on }}
95 # source needs to be at the following location relative to the build dir:
152 # The build time
[all...]
H A Ddocs.yml6 name: "Test documentation build"
52 check-docs-build:
53 name: "Test documentation build"
116 sudo apt-get install -y cmake ninja-build swig graphviz
119 - name: Build LLVM docs
124 cmake -B llvm-build -GNinja -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_SPHINX=ON ./llvm
125 TZ=UTC ninja -C llvm-build docs-llvm-html docs-llvm-man
127 cp -r llvm-build/docs/* built-docs/llvm/
128 - name: Build Clang docs
133 cmake -B clang-build
[all...]
/llvm-project/polly/lib/External/isl/include/isl/
H A Dast_build.h46 isl_ctx *isl_ast_build_get_ctx(__isl_keep isl_ast_build *build);
54 __isl_keep isl_ast_build *build);
57 __isl_keep isl_ast_build *build);
60 __isl_take isl_ast_build *build, __isl_take isl_set *set);
63 __isl_keep isl_ast_build *build);
65 __isl_take isl_ast_build *build);
68 __isl_take isl_ast_build *build,
71 __isl_take isl_ast_build *build,
75 __isl_take isl_ast_build *build,
77 __isl_keep isl_ast_build *build, void *user), void *user);
[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
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.
37 In a simple two-stage bootstrap build, we build clang using the system compiler,
38 then use that just-built clang to build clang again. In CMake this simplest form
[all …]
/llvm-project/utils/bazel/
H A D.bazelrc17 # Prevent invalid caching if input files are modified during a build.
18 build --experimental_guard_against_concurrent_changes
21 build --enable_platform_specific_config
28 build:linux --force_pic
29 build:windows --force_pic
33 build --dynamic_mode=off
37 build --strip=never
40 build --features=layering_check
44 # See: https://bazel.build/reference/be/functions#exports_files
45 build
[all...]
/llvm-project/llvm/test/DebugInfo/PDB/Native/
H A Dpdb-native-compilands.test21 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\_cpu_disp_.obj
22 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\_initsect_.obj
23 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\_sehprolg4_.obj
24 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\_chandler4gs_.obj
25 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\_secchk_.obj
26 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\gs_cookie.obj
27 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\gs_report.obj
28 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\gs_support.obj
29 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\checkcfg.obj
30 BIGREAD: f:\dd\vctools\crt\vcstartup\build\md\msvcrt_kernel32\obj1r\i386\guard_support.obj
[all …]
/llvm-project/llvm/utils/gn/
H A DREADME.rst13 *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
27 just parts of LLVM, and embedding the LLVM GN build from other builds are
28 non-goals for the GN build.
[all …]
/llvm-project/clang-tools-extra/clangd/test/Inputs/background-index/
H A Ddefinition.jsonrpc.tmpl25 # BUILD: "method": "$/progress"
26 # BUILD-NEXT: "params": {
27 # BUILD-NEXT: "token": "backgroundIndexProgress",
28 # BUILD-NEXT: "value": {
29 # BUILD-NEXT: "kind": "begin",
30 # BUILD-NEXT: "percentage": 0,
31 # BUILD-NEXT: "title": "indexing"
32 # BUILD-NEXT: }
33 # BUILD-NEXT: }
34 # BUILD: "method": "$/progress"
[all …]
/llvm-project/lld/test/ELF/
H A Dbuild-id.s5 # RUN: ld.lld --build-id %t -o %t2
8 # RUN: ld.lld --build-id %t -o %t2
10 # RUN: ld.lld --build-id %t -o %t2 --threads=1
13 # RUN: ld.lld --build-id=fast %t -o %t2
16 # RUN: ld.lld --build-id=md5 %t -o %t2
18 # RUN: ld.lld --build-id=md5 %t -o %t2 --threads=1
21 # RUN: ld.lld --build-id=sha1 %t -o %t2
23 # RUN: ld.lld --build-id=sha1 %t -o %t2 --threads=1
26 # RUN: ld.lld --build-id=tree %t -o %t2
28 # RUN: ld.lld --build-id=tree %t -o %t2 --threads=1
[all …]
/llvm-project/libc/AOR_v20.02/math/
H A DDir.mk8 B := build/math
18 math-includes := $(patsubst $(S)/%,build/%,$(wildcard $(S)/include/*.h))
21 build/lib/libmathlib.so \
22 build/lib/libmathlib.a \
25 build/bin/mathtest \
26 build/bin/mathbench \
27 build/bin/mathbench_libc \
28 build/bin/runulp.sh \
29 build/bin/ulp \
32 build/bin/rtest \
[all …]
/llvm-project/third-party/benchmark/
H A DREADME.md3 [![build-and-test](https://github.com/google/benchmark/workflows/build-and-test/badge.svg)](https:/…
53 The library can be used with C++03. However, it requires C++11 to build,
56 The following minimum versions are required to build the library:
63 See [Platform-Specific Build Instructions](docs/platform_specific_build_instructions.md).
71 versions of build tools._
78 # Make a build directory to place the build output.
79 $ cmake -E make_directory "build"
80 # Generate build system files with cmake, and download any dependencies.
81 $ cmake -E chdir "build" cmake -DBENCHMARK_DOWNLOAD_DEPENDENCIES=on -DCMAKE_BUILD_TYPE=Release ../
83 # cmake -DCMAKE_BUILD_TYPE=Release -S . -B "build"
[all …]
/llvm-project/clang/tools/scan-build/
H A DCMakeLists.txt1 option(CLANG_INSTALL_SCANBUILD "Install the scan-build tool" ON)
7 scan-build
8 scan-build.bat
18 scan-build
32 scan-build.1)
51 COMPONENT scan-build)
65 COMPONENT scan-build)
79 COMPONENT scan-build)
83 add_custom_command(OUTPUT ${CMAKE_BINARY_DIR}/share/scan-build/${ShareFile}
85 ${CMAKE_BINARY_DIR}/share/scan-build
[all …]
/llvm-project/clang/test/Modules/
H A Dexplicit-build.cpp4 // Build chained modules A, B, and C
5 …d=c++11 -fmodules -fimplicit-module-maps -fmodules-cache-path=%t -Rmodule-build -fno-modules-error…
6 // RUN: -fmodule-name=a -emit-module %S/Inputs/explicit-build/module.modulemap -o %t/a.p…
7 // RUN: 2>&1 | FileCheck --check-prefix=CHECK-NO-IMPLICIT-BUILD %s --allow-empty
9 …d=c++11 -fmodules -fimplicit-module-maps -fmodules-cache-path=%t -Rmodule-build -fno-modules-error…
11 // RUN: -fmodule-name=b -emit-module %S/Inputs/explicit-build/module.modulemap -o %t/b.p…
12 // RUN: 2>&1 | FileCheck --check-prefix=CHECK-NO-IMPLICIT-BUILD %s --allow-empty
14 …d=c++11 -fmodules -fimplicit-module-maps -fmodules-cache-path=%t -Rmodule-build -fno-modules-error…
16 // RUN: -fmodule-name=c -emit-module %S/Inputs/explicit-build/module.modulemap -o %t/c.p…
17 // RUN: 2>&1 | FileCheck --check-prefix=CHECK-NO-IMPLICIT-BUILD %s --allow-empty
[all …]

12345678910>>...176