| /llvm-project-15.0.7/polly/lib/External/isl/ |
| H A D | isl_multi_param_templ.c | 27 isl_bool involved = FN(EL,involves_param_id)(multi->u.p[i], id); in FN() local
28 if (involved < 0 || involved) in FN()
29 return involved; in FN()
|
| /llvm-project-15.0.7/llvm/test/MC/Hexagon/ |
| H A D | dealloc-return-jump.s | 3 # dealloc_return cannot be involved in a double jump packet
|
| /llvm-project-15.0.7/llvm/test/Transforms/SimplifyCFG/ |
| H A D | PHINode.ll | 1 …lifycfg-require-and-preserve-domtree=1 is not folding blocks if there is a PHI node involved. This
|
| H A D | fold-debug-location.ll | 28 ; All instructions involved in folding have the same !dbg location. Make sure
|
| /llvm-project-15.0.7/ |
| H A D | CONTRIBUTING.md | 8 describes how to get involved, raise issues and submit patches. Please note
|
| /llvm-project-15.0.7/llvm/docs/ |
| H A D | ResponseGuide.rst | 115 * Reminder of confidentiality policy regarding the report and parties involved
187 individual(s) involved and request to stop this behavior. This conversation
225 * Statements from other individuals involved in the incident to support the
237 one of the involved parties, or anything else that may make it harder to remain
247 unpleasant for everyone involved.
250 involved in the response process. The rest of the committee will meet and
262 member is involved in a report, the member will be asked to recuse themselves
|
| H A D | ReportingGuide.rst | 55 * Names or descriptions of anyone who was involved or who witnessed the
76 Conduct committee members. In the case that a CoC committee member is involved
|
| /llvm-project-15.0.7/llvm/test/tools/llvm-objcopy/ELF/Inputs/ |
| H A D | compress-debug-sections.yaml | 24 ## This section should not be involved in relocations.
|
| /llvm-project-15.0.7/polly/test/ScopInfo/ |
| H A D | aliasing_many_parameters_not_all_involved.ll | 4 ; Check that we allow this SCoP even though it has 10 parameters involved in posisbly aliasing acce…
5 ; However, only 7 are involved in accesses through B, 8 through C and none in accesses through A.
|
| /llvm-project-15.0.7/llvm/test/CodeGen/X86/ |
| H A D | merge-sp-update-lea.ll | 5 ; Check that the merging of SP updates, when LEAs are involved, happen
|
| H A D | lsr-normalization.ll | 7 ; one loop involved with the increment value for an addrec on another
|
| /llvm-project-15.0.7/compiler-rt/lib/memprof/ |
| H A D | memprof_flags.inc | 28 "If set, prints thread creation stacks for the threads involved in the "
|
| /llvm-project-15.0.7/llvm/test/Transforms/LoopSimplify/ |
| H A D | indirectbr.ll | 5 ; LoopSimplify should not try to transform loops when indirectbr is involved.
|
| /llvm-project-15.0.7/llvm/test/CodeGen/SystemZ/ |
| H A D | dag-combine-03.ll | 5 ; BITCAST nodes are involved on a big-endian target.
|
| H A D | cond-move-05.mir | 5 # involved.
|
| /llvm-project-15.0.7/llvm/test/Transforms/Inline/X86/ |
| H A D | call-abi-compatibility.ll | 79 ; This call should get inlined, because only simple types are involved.
|
| /llvm-project-15.0.7/llvm/test/DebugInfo/X86/ |
| H A D | dbg-value-funcarg3.ll | 11 ; Catch metadata references for involved variables.
|
| /llvm-project-15.0.7/llvm/test/CodeGen/ARM/ |
| H A D | peephole-phi.mir | 84 # operands are involved.
|
| /llvm-project-15.0.7/llvm/docs/HistoricalNotes/ |
| H A D | 2001-06-01-GCCOptimizations.txt | 48 that it can be made to work, but might be a little more involved than we
|
| /llvm-project-15.0.7/mlir/docs/Dialects/ |
| H A D | Vector.md | 78 ]]]>`. There are tradeoffs involved related to how one can access subvectors and
252 This section describes the tradeoffs involved in lowering the MLIR n-D vector
283 There are multiple tradeoffs involved in choosing one or the other that we
321 There are multiple tradeoffs involved that mix implications on the programming
419 Different HW will require different tradeoffs in the sizes involved in steps 1.,
446 involved. For example, `vector.cast %0: vector<K1x...xKnxf32> to vector<Kxf32>`
|
| /llvm-project-15.0.7/llvm/docs/GlobalISel/ |
| H A D | IRTranslator.rst | 11 occasionally get a bit more involved. For example:
|
| /llvm-project-15.0.7/llvm/test/TableGen/ |
| H A D | self-reference.td | 99 // references are involved.
|
| /llvm-project-15.0.7/compiler-rt/lib/tsan/rtl/ |
| H A D | tsan_flags.inc | 81 "If set, prints thread creation stacks for the threads involved in "
|
| /llvm-project-15.0.7/mlir/test/Dialect/SparseTensor/ |
| H A D | sparse_scalars.mlir | 7 // in which scalar values can be involved in a sparse kernel
|
| /llvm-project-15.0.7/lld/test/ELF/lto/ |
| H A D | wrap-2.ll | 3 ;; the wrapped symbol, when LTO or ThinLTO is involved. It checks for various
|