Home
last modified time | relevance | path

Searched refs:possible (Results 1 – 25 of 784) sorted by relevance

12345678910>>...32

/llvm-project-15.0.7/llvm/lib/Target/Mips/
H A DMSA.txt4 Intrinsics are lowered to SelectionDAG nodes where possible in order to enable
18 It is not possible to emit bclri.b since andi.b covers exactly the
23 It is not possible to emit vshf.w when the shuffle description is
36 It is not possible to emit ilvl.d, or pckev.d since ilvev.d covers the
40 It is not possible to emit ilvr.d, or pckod.d since ilvod.d covers the
48 It is not possible to emit splati.w since shf.w covers the same cases.
66 It is (currently) not possible to emit bmz.v, or bsel.v since bmnz.v is
/llvm-project-15.0.7/llvm/include/llvm/TableGen/
H A DAutomaton.td23 // Q: A set of possible states.
28 // Because generating all possible states is tedious, we instead define the
40 // Instead of defining all possible states (which would be cumbersome), the user
41 // provides a set of possible Transitions from state A, consuming an input
44 // all the possible transitions until none are valid.
92 // The automaton generator uses this property to crawl the set of possible
/llvm-project-15.0.7/llvm/test/CodeGen/AArch64/
H A Dmachine-outliner-all-stack.mir4 # Show that, when instructions that use the stack are present, it's possible
6 # It's possible for reg-save-possible to outline by storing LR to a register,
12 define void @reg-save-possible() #0 { ret void }
20 name: reg-save-possible
30 ; CHECK-LABEL: name: reg-save-possible
/llvm-project-15.0.7/llvm/test/CodeGen/PowerPC/
H A Dinline-asm-scalar-to-vector-error.ll4 ; CHECK: scalar-to-vector conversion failed, possible invalid constraint for vector type
7 ; CHECK: scalar-to-vector conversion failed, possible invalid constraint for vector type
/llvm-project-15.0.7/llvm/test/CodeGen/ARM/
H A D2012-09-25-InlineAsmScalarToVectorConv2.ll4 ; CHECK: scalar-to-vector conversion failed, possible invalid constraint for vector type
5 ; CHECK: scalar-to-vector conversion failed, possible invalid constraint for vector type
/llvm-project-15.0.7/llvm/test/MC/Hexagon/
H A Dbug_28748.s4 # possible compounds. Compounding all possible opcodes is ideal for code size
/llvm-project-15.0.7/llvm/test/CodeGen/SystemZ/
H A Dshift-09.ll17 ; Check that we use SLL over SLLK where possible.
39 ; Check that we use SRL over SRLK where possible.
61 ; Check that we use SRA over SRAK where possible.
/llvm-project-15.0.7/llvm/test/tools/obj2yaml/ELF/
H A Drelocation-addend.yaml7 ## We use 1 as it is the first possible positive value.
17 ## We use -1 as it is the first possible negative value.
59 ## We use 1 as it is the first possible positive value.
69 ## We use -1 as it is the first possible negative value.
/llvm-project-15.0.7/mlir/lib/Dialect/SPIRV/Linking/ModuleCombiner/
H A DModuleCombiner.cpp41 auto possible = StringAttr::get(ctx, newSymName + Twine(++lastUsedID)); in renameSymbol() local
42 if (!SymbolTable::lookupSymbolIn(module, possible)) in renameSymbol()
43 return possible; in renameSymbol()
/llvm-project-15.0.7/clang/test/SemaObjC/
H A Dstrong-in-c-struct.m28 L0: // expected-note {{possible target of indirect goto}}
51 L0: // expected-note {{possible target of indirect goto}}
70 L0: // expected-note {{possible target of indirect goto}}
/llvm-project-15.0.7/llvm/test/CodeGen/AMDGPU/GlobalISel/
H A Dsmrd.ll20 ; SMRD load with the largest possible immediate offset.
32 ; SMRD load with an offset greater than the largest possible immediate.
62 ; SMRD load with the largest possible immediate offset on VI
78 ; SMRD load with an offset greater than the largest possible immediate on VI
/llvm-project-15.0.7/llvm/docs/
H A DBenchmarking.rst9 For benchmarking a patch we want to reduce all possible sources of
10 noise as much as possible. How to do that is very OS dependent.
24 * Disable as many processes or services as possible on the target system.
/llvm-project-15.0.7/lldb/docs/resources/
H A Dcaveats.rst17 To make this possible, LLDB links against the Python shared library. Linking
20 1. It is not possible to build and link LLDB against a Python 3 library and
23 2. It is not possible to build and link LLDB against one distribution on
/llvm-project-15.0.7/llvm/test/FileCheck/
H A Dnumeric-defines.txt35 NUMERRMSG1: defines.txt:[[#@LINE-10]]:1: note: possible intended match here
40 NUMERRMSG2: defines.txt:[[#@LINE-14]]:1: note: possible intended match here
86 NUMERRMSG3: defines.txt:[[#@LINE-10]]:1: note: possible intended match here
91 NUMERRMSG4: defines.txt:[[#@LINE-14]]:1: note: possible intended match here
/llvm-project-15.0.7/openmp/docs/remarks/
H A DOMP140.rst3 Could not internalize function. Some optimizations may not be possible. [OMP140]
42 be possible. [OMP140]
/llvm-project-15.0.7/libc/docs/
H A Dlayering.rst5 When meaningful and practically possible on a platform, llvm-libc will be
6 developed in a fashion that it will be possible to layer it over the system
/llvm-project-15.0.7/llvm/test/tools/llvm-readobj/ELF/
H A Dreloc-addends.test64 ## Addend == max possible int64 == 0x7FFFFFFFFFFFFFFF.
67 ## Addend == min possible int64 == 0x8000000000000000.
138 ## Addend == max possible int32 == 0x7FFFFFFF.
141 ## Addend == min possible int32 == 0x80000000.
H A Dsection-flags-os-proc.test56 # OS-PROC-LLVM: Name: .all.possible
87 # OS-PROC-GNU-NEXT: [11] .all.possible PROGBITS 0000000000000000 000040 000000 00 WAXMSIL…
133 ## Set all possible flags to test where we print 'o' and 'p' letters.
134 - Name: .all.possible
H A Dlinker-options.test10 …ection at index 2 is broken: an incomplete key-value pair was found. The last possible key was: "c"
47 ## Case 5: check we report a warning when it is not possible to read
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/bugprone/
H A Dnot-null-terminated-result.rst6 Finds function calls where it is possible to cause a not null-terminated result.
47 It is possible to rewrite the ``memcpy()`` and ``memcpy_s()`` calls as the
60 :option:`WantToUseSafeFunctions` is set to `true` and it is possible to
71 [1] It is possible to overflow:
/llvm-project-15.0.7/clang/docs/
H A DDebuggingCoroutines.rst18 debug information is highly language specific. However, this is not possible
40 possible return type of one of these `coroutine functions`. `Task` and
105 It is also possible to print the `promise_type` of a coroutine from the address
114 This is possible because the `promise_type` is guaranteed by the ABI to be at a
124 be removed during optimization, so this method may not be possible.
139 Just as printing the `promise_type` is possible from the coroutine address,
140 printing the details of the coroutine frame from an address is also possible:
154 The above is possible because:
374 possible, this task is not recommended in production code as it is costly at
H A DDataFlowAnalysisIntro.md44 imagine that we want to track possible values of an integer variable in our
63 We use sets of integers to represent possible values of `x`. Local variables
65 between statements with sets of possible values.
118 3 possible values, we stop tracking specific values at that program point.
132 The statement "at this program point, `x`'s possible values are `⊤`" is
136 Note that we can get more than 3 possible values even without a loop:
153 When `x` is declared but not initialized, it has no possible values. We
175 lattice that we can use in practice to track possible values of integer
184 compute the sets of possible values algorithmically.
225 The sets of possible values are influenced by:
[all …]
/llvm-project-15.0.7/llvm/test/tools/yaml2obj/ELF/
H A Doutput-limit.yaml2 ## Check it is possible to change this limit using the
35 ## Another possible case is when an alignment gap inserted
/llvm-project-15.0.7/mlir/include/mlir/Dialect/Tensor/IR/
H A DTensorBase.td24 We leave it to other dialects to hold the vast swath of possible
39 scope as much as possible. The expectation is that at some point
/llvm-project-15.0.7/mlir/utils/vscode/.vscode/
H A Dlaunch.json2 // Use IntelliSense to learn about possible attributes.

12345678910>>...32