| /llvm-project-15.0.7/libclc/generic/include/clc/geometric/ |
| H A D | cross.h | 1 _CLC_OVERLOAD _CLC_DECL float3 cross(float3 p0, float3 p1); 2 _CLC_OVERLOAD _CLC_DECL float4 cross(float4 p0, float4 p1); 5 _CLC_OVERLOAD _CLC_DECL double3 cross(double3 p0, double3 p1); 6 _CLC_OVERLOAD _CLC_DECL double4 cross(double4 p0, double4 p1);
|
| /llvm-project-15.0.7/llvm/test/DebugInfo/ |
| H A D | cross-cu-inlining.test | 1 RUN: llvm-symbolizer --obj=%p/Inputs/cross-cu-inlining.x86_64-macho.o 0x17 | FileCheck %s 4 ; to resolve the cross-cu reference and retrieve func's name 6 CHECK-NEXT: /tmp{{[/\\]}}cross-cu-inlining.c:16:3 8 CHECK-NEXT: /tmp{{[/\\]}}cross-cu-inlining.c:11:0
|
| /llvm-project-15.0.7/llvm/test/tools/llvm-dwarfdump/X86/ |
| H A D | simplified-template-names.s | 4 # Checking the LLVM side of cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/simplified_tem… 24 ….loc 0 142 0 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… 34 ….loc 0 142 44 prologue_end # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… 48 ….loc 0 182 0 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… 58 ….loc 0 184 8 prologue_end # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… 61 ….loc 0 185 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… 63 ….loc 0 186 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… 65 ….loc 0 187 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… 67 ….loc 0 188 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… 69 ….loc 0 189 3 # cross-project-tests/debuginfo-tests/clang_llvm_roundtrip/si… [all …]
|
| /llvm-project-15.0.7/llvm/test/Transforms/CrossDSOCFI/ |
| H A D | thumb.ll | 1 ; RUN: opt -mtriple=armv7-linux-android -S -cross-dso-cfi < %s | FileCheck --check-prefix=THUMB %s 2 ; RUN: opt -mtriple=thumbv7-linux-android -S -cross-dso-cfi < %s | FileCheck --check-prefix=THUMB %s 3 ; RUN: opt -mtriple=i386-linux -S -cross-dso-cfi < %s | FileCheck --check-prefix=NOTHUMB %s 4 ; RUN: opt -mtriple=x86_64-linux -S -cross-dso-cfi < %s | FileCheck --check-prefix=NOTHUMB %s
|
| H A D | cfi_functions.ll | 2 ; RUN: opt -S -cross-dso-cfi < %s | FileCheck %s 3 ; RUN: opt -S -passes=cross-dso-cfi < %s | FileCheck %s
|
| H A D | basic.ll | 1 ; RUN: opt -S -cross-dso-cfi < %s | FileCheck %s 2 ; RUN: opt -S -passes=cross-dso-cfi < %s | FileCheck %s
|
| /llvm-project-15.0.7/libclc/generic/lib/geometric/ |
| H A D | cross.cl | 3 _CLC_OVERLOAD _CLC_DEF float3 cross(float3 p0, float3 p1) { 8 _CLC_OVERLOAD _CLC_DEF float4 cross(float4 p0, float4 p1) { 16 _CLC_OVERLOAD _CLC_DEF double3 cross(double3 p0, double3 p1) { 21 _CLC_OVERLOAD _CLC_DEF double4 cross(double4 p0, double4 p1) {
|
| /llvm-project-15.0.7/clang/docs/ |
| H A D | CrossCompilation.rst | 9 for cross-compiling your code to a different architecture. It assumes you 17 `instructions for cross-compiling LLVM itself 22 for performing cross-compilation. 40 But, as is true to any cross-compiler, and given the complexity of 136 There are two main ways to have a cross-compiler: 138 #. When you have extracted your cross-compiler from a zip file into 148 distributions have cross-compiler packages available), make 150 cross-compiler toolchain. 165 cross-compiled to your target, and your build system will probably 170 So, if the build system is not aware that you want to cross-compile [all …]
|
| H A D | ControlFlowIntegrity.rst | 44 Experimental support for :ref:`cross-DSO control flow integrity 45 <cfi-cross-dso>` exists that does not require classes to have hidden LTO 46 visibility. This cross-DSO support has unstable ABI at this time. 237 ``-fsanitize-cfi-cross-dso``. 250 relevant for users of cross-DSO CFI: 263 possible with LTO in the intra-DSO case, but in the cross-DSO case the only 277 especially in cross-DSO mode which normally preserves function address 334 This scheme is currently not compatible with cross-DSO CFI or the 364 .. _cfi-cross-dso: 369 Use **-f[no-]sanitize-cfi-cross-dso** to enable the cross-DSO control [all …]
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | HowToCrossCompileLLVM.rst | 11 For more information on how to use Clang as a cross-compiler, 20 system, cross-compiling from an x86_64 host (most Intel and AMD chips 30 * ``libgcc1-armhf-cross`` 31 * ``libsfgcc1-armhf-cross`` 32 * ``libstdc++6-armhf-cross`` 33 * ``libstdc++6-4.7-dev-armhf-cross`` 63 * ``--target=arm-linux-gnueabihf`` or whatever is the triple of your cross GCC. 66 * Appropriate use of ``-I`` and ``-L``, depending on how the cross GCC is installed, 73 using Clang as a cross-compiler, you will *also* have to set ``--sysroot`` 97 #. If you're using Clang as the cross-compiler, there is a problem in [all …]
|
| H A D | HowToBuildOnARM.rst | 11 This document is *NOT* tailored to help you cross-compile LLVM/Clang 13 out more about cross-compiling, please check :doc:`HowToCrossCompileLLVM`. 29 you'll use an ARM board to cross-compile to other arches. If you're
|
| /llvm-project-15.0.7/cross-project-tests/ |
| H A D | CMakeLists.txt | 69 add_lit_testsuite(check-cross-project "Running cross-project tests" 88 # Add check-cross-project-* targets. 93 set_target_properties(check-cross-project PROPERTIES FOLDER "Tests")
|
| /llvm-project-15.0.7/llvm/test/ExecutionEngine/MCJIT/ |
| H A D | cross-module-a.ll | 1 ; RUN: %lli -jit-kind=mcjit -extra-module=%p/Inputs/cross-module-b.ll %s > /dev/null 2 ; RUN: %lli -extra-module=%p/Inputs/cross-module-b.ll %s > /dev/null
|
| H A D | cross-module-sm-pic-a.ll | 1 ; RUN: %lli -jit-kind=mcjit -extra-module=%p/Inputs/cross-module-b.ll -relocation-model=pic -code-m… 2 ; RUN: %lli -lljit-platform=Inactive -extra-module=%p/Inputs/cross-module-b.ll -relocation-model=pi…
|
| /llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/ |
| H A D | fold-readlane.mir | 105 # GCN-LABEL: name: fold-imm-readfirstlane-cross-block{{$}} 109 name: fold-imm-readfirstlane-cross-block 122 # GCN-LABEL: name: fold-copy-readfirstlane-cross-block{{$}} 126 name: fold-copy-readfirstlane-cross-block 138 # GCN-LABEL: name: fold-copy-readfirstlane-cross-block-exec-def{{$}} 143 name: fold-copy-readfirstlane-cross-block-exec-def 174 # GCN-LABEL: name: fold-imm-readfirstlane-cross-block-exec-def{{$}} 180 name: fold-imm-readfirstlane-cross-block-exec-def
|
| /llvm-project-15.0.7/llvm/test/MC/PowerPC/ |
| H A D | ppc64-prefix-align.s | 7 # cross 64 byte boundaries. If an 8 byte instruction is about to cross such 9 # 4 bytes later and does not cross the boundary.
|
| /llvm-project-15.0.7/llvm/tools/llvm-config/ |
| H A D | CMakeLists.txt | 10 # entire thing is overkill. Avoiding that especially saves on build time when cross 11 # compiling LLVM and building both cross and native `llvm-config`s. We don't 12 # want to build an entire native libLLVM.so in addition to the cross one just
|
| /llvm-project-15.0.7/llvm/projects/ |
| H A D | CMakeLists.txt | 14 (NOT ${entry} STREQUAL ${CMAKE_CURRENT_SOURCE_DIR}/cross-project-tests)) 46 add_llvm_external_project(cross-project-tests)
|
| /llvm-project-15.0.7/libc/AOR_v20.02/ |
| H A D | config.mk.dist | 31 # Use for cross compilation with gcc. 34 # Use with cross testing.
|
| /llvm-project-15.0.7/lld/test/wasm/ |
| H A D | reloc-relative.s | 15 # internal cross segment subtraction 25 # external cross segment subtraction
|
| /llvm-project-15.0.7/llvm/test/MC/COFF/ |
| H A D | cross-section-relative.ll | 12 ;;;; cross-section relative relocations 31 ;;;; cross-section relative with source offset
|
| /llvm-project-15.0.7/libclc/test/ |
| H A D | cross.cl | 2 *f = cross(f[0], f[1]);
|
| /llvm-project-15.0.7/bolt/test/runtime/ |
| H A D | lit.local.cfg | 1 # Tests are not expected to pass in a cross-compilation setup.
|
| /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/llgdb-tests/ |
| H A D | lit.local.cfg | 1 # debuginfo-tests are not expected to pass in a cross-compilation setup.
|
| /llvm-project-15.0.7/llvm/test/ExecutionEngine/ |
| H A D | lit.local.cfg | 4 # ExecutionEngine tests are not expected to pass in a cross-compilation setup.
|