Home
last modified time | relevance | path

Searched full:them (Results 1 – 25 of 4177) sorted by relevance

12345678910>>...168

/llvm-project/clang/test/SemaCXX/
H A Dwarn-unsafe-buffer-usage-multi-decl-warnings.cpp9 …ve bounds information, and change 'q' to 'std::span' to propagate bounds information between them}} in local_assign_both_span()
12 …ve bounds information, and change 'p' to 'std::span' to propagate bounds information between them}} in local_assign_both_span()
35 …ve bounds information, and change 'q' to 'std::span' to propagate bounds information between them}} in local_assign_lhs_span()
46 …rmation, and change 'c', 'b', and 'a' to 'std::span' to propagate bounds information between them}} in lhs_span_multi_assign()
60 …s information, and change 'q' and 'r' to 'std::span' to propagate bounds information between them}} in rhs_span1()
62 …s information, and change 'p' and 'q' to 'std::span' to propagate bounds information between them}} in rhs_span1()
109 …s information, and change 'r' and 'q' to 'std::span' to propagate bounds information between them}} in foo1b()
112 …s information, and change 'p' and 'r' to 'std::span' to propagate bounds information between them}} in foo1b()
129 …s information, and change 'q' and 'r' to 'std::span' to propagate bounds information between them}} in foo2a()
147 …s information, and change 'q' and 'r' to 'std::span' to propagate bounds information between them}} in foo2c()
[all …]
H A Dwarn-unsafe-buffer-usage-multi-decl-ptr-init.cpp7 …rmation, and change 'c', 'b', and 'a' to 'std::span' to propagate bounds information between them}} in lhs_span_multi_assign()
13 …s information, and change 'q' and 'r' to 'std::span' to propagate bounds information between them}} in rhs_span1()
15 …s information, and change 'p' and 'q' to 'std::span' to propagate bounds information between them}} in rhs_span1()
21 …ve bounds information, and change 'q' to 'std::span' to propagate bounds information between them}} in rhs_span2()
48 …s information, and change 'q' and 'r' to 'std::span' to propagate bounds information between them}} in test_crash()
H A Dwarn-unsafe-buffer-usage-multi-decl-uuc.cpp15 …ve bounds information, and change 'r' to 'std::span' to propagate bounds information between them}} in uuc_if_body()
23 …ve bounds information, and change 'r' to 'std::span' to propagate bounds information between them}} in uuc_if_body1()
32 …ve bounds information, and change 'r' to 'std::span' to propagate bounds information between them}} in uuc_if_body2()
45 …ve bounds information, and change 'r' to 'std::span' to propagate bounds information between them}} in uuc_if_body2_ptr_init()
/llvm-project/libc/src/setjmp/arm/
H A Dlongjmp.cpp25 # Reload r8, r9. They cannot appear in register lists so load them
26 # into the lower registers, then move them into place.
31 # Reload r10, r11. They cannot appear in register lists so load them
32 # into the lower registers, then move them into place.
37 # Reload sp, lr. They cannot appear in register lists so load them
38 # into the lower registers, then move them into place.
/llvm-project/llvm/test/CodeGen/AMDGPU/
H A Dinline-asm-reserved-regs.ll4 ; ERR: note: Reserved registers on the clobber list may not be preserved across the asm statement, and clobbering them may lead to undefined behaviour.
12 ; ERR: note: Reserved registers on the clobber list may not be preserved across the asm statement, and clobbering them may lead to undefined behaviour.
20 ; ERR: note: Reserved registers on the clobber list may not be preserved across the asm statement, and clobbering them may lead to undefined behaviour.
28 ; ERR: note: Reserved registers on the clobber list may not be preserved across the asm statement, and clobbering them may lead to undefined behaviour.
36 ; ERR: note: Reserved registers on the clobber list may not be preserved across the asm statement, and clobbering them may lead to undefined behaviour.
/llvm-project/clang/lib/Driver/ToolChains/
H A DFlang.h27 /// Extract fortran dialect options from the driver arguments and add them to
35 /// Extract preprocessing options from the driver arguments and add them to
43 /// Extract PIC options from the driver arguments and add them to
51 /// Extract target options from the driver arguments and add them to
101 /// Extract offload options from the driver arguments and add them to
112 /// Extract options for code generation from the driver arguments and add them
120 /// Extract other compilation options from the driver arguments and add them in hasIntegratedCPP()
/llvm-project/clang/test/Analysis/Checkers/
H A DRunLoopAutoreleaseLeakChecker.m32 …ed by the launch of main run loop may never get released; consider moving them to a separate autor…
51 …ollowed by the launch of xpc_main may never get released; consider moving them to a separate autor…
59 …ed by the launch of main run loop may never get released; consider moving them to a separate autor…
84 …ed by the launch of main run loop may never get released; consider moving them to a separate autor…
94 …ed by the launch of main run loop may never get released; consider moving them to a separate autor…
125 …ollowed by the launch of xpc_main may never get released; consider moving them to a separate autor…
159 …ed by the launch of main run loop may never get released; consider moving them to a separate autor…
/llvm-project/llvm/include/llvm/Support/
H A DTargetSelect.h10 // linked into the main application executable, and initialize them as
53 /// support, to make them available via the TargetRegistry.
63 /// support, to make them available via the TargetRegistry.
76 /// support, to make them available via the TargetRegistry.
85 /// it wants all asm printers that LLVM is configured to support, to make them
95 /// wants all asm parsers that LLVM is configured to support, to make them
106 /// them available via the TargetRegistry.
/llvm-project/lld/docs/
H A DNewLLD.rst14 files in the usual way and give them to the linker. It is naturally expected to
53 until we need them to continue linking.
132 and inserting all of them to a hash table takes 1.5 seconds.
143 be understood as the interactions between them. Once you understand their
194 and how to apply relocations to them.
196 and how to apply them.
224 a file. It creates OutputSections, put all InputSections/Chunks into them,
225 assign unique, non-overlapping addresses and file offsets to them, and then
226 write them down to a file.
246 with all bitcode files to convert them to one big regular ELF/COFF file.
/llvm-project/flang/docs/
H A DModFiles.md91 It might be possible to anonymize private names if users don't want them exposed
96 A module that contains `USE` statements needs them represented in the
106 have been listed in *only-list*s). In that case collapse them into a single *use-stmt*.
114 for module files and where to write them. By default it will be the current
119 search for them. gfortran is similar except it uses `-J` instead of `-module`.
165 wrote them we would have to save some amount of provenance information in the
/llvm-project/clang/unittests/Tooling/RecursiveASTVisitorTests/
H A DConstructExpr.cpp42 // to use them in order to force them to appear in the AST.
58 // to use them in order to force them to appear in the AST.
/llvm-project/lldb/source/Plugins/Platform/MacOSX/
H A DPlatformDarwinKernel.h138 // A dSYM bundle may have multiple DWARF binaries in them, so a vector
170 /// next to them.
174 /// dSYMs next to them.
184 /// to them.
188 /// them.
191 /// List of kernel dsyms with no binaries next to them.
/llvm-project/llvm/docs/HistoricalNotes/
H A D2003-01-23-CygwinNotes.txt18 change them to have .a's.
26 does not like = signs in rules. Burg's gram.yc source file uses them. I think
27 you can just take them out.
/llvm-project/mlir/python/mlir/dialects/linalg/opdsl/ops/
H A Dcore_named_ops.py397 them to the same data type as the accumulator/output. The quantized variant
418 them to the same data type as the accumulator/output.
436 them to the same data type as the accumulator/output.
496 them to the same data type as the accumulator/output.
515 them to the same data type as the accumulator/output.
534 them to the same data type as the accumulator/output.
554 them to the same data type as the accumulator/output. The quantized variant
574 them to the same data type as the accumulator/output.
590 them to the same data type as the accumulator/output.
604 them t
[all...]
/llvm-project/llvm/test/CodeGen/X86/
H A Dnot-and-simplify.ll5 ; Clear high bits via shift, set them with xor (not), then mask them off.
33 ; Clear low bits via shift, set them with xor (not), then mask them off.
/llvm-project/compiler-rt/test/memprof/TestCases/
H A Dtest_memintrin.cpp9 // but we need to look for them in the same CHECK to get the correct STACKIDP.
16 // but we need to look for them in the same CHECK to get the correct STACKIDQ.
28 // but we need to look for them in the same CHECK-DAG. in main()
36 // but we need to look for them in the same CHECK-DAG. in main()
/llvm-project/mlir/test/Dialect/Shape/
H A Dinvalid.mlir93 …e of the operands can hold error values then the result must be of type `shape` to propagate them}}
110 …ne of the operands can hold error values then the result must be of type `size` to propagate them}}
119 …ne of the operands can hold error values then the result must be of type `size` to propagate them}}
127 …ne of the operands can hold error values then the result must be of type `size` to propagate them}}
135 …ne of the operands can hold error values then the result must be of type `size` to propagate them}}
143 …ne of the operands can hold error values then the result must be of type `size` to propagate them}}
151 …e of the operands can hold error values then the result must be of type `shape` to propagate them}}
161 …e of the operands can hold error values then the result must be of type `shape` to propagate them}}
/llvm-project/llvm/docs/
H A DMergeFunctions.rst16 The main purpose of this pass is to recognize such functions and merge them.
87 of them. But how do we detect duplicates? This is the idea: we split functions
134 all of them in a special hash-table. Functions with equal hashes are equal.
184 case, we remove them from ``FnTree``, and mark them to be rescanned, namely
185 put them into ``Deferred`` list.
210 equal functions *F`* in the shortest time possible , and merge them into a
218 following this rule, then evaluate which of them is greater. What kind of rule
237 "sub-comparison-routines", with each of them also consisting of
318 compare them by “``FunctionComparator::compare(const BasicBlock*, const
333 preference to one of them. So proceed to the next step.
[all …]
/llvm-project/libc/docs/
H A Dcontributing.rst40 #. **Update the clang-tidy lint rules and use them in the build and/or CI** -
43 them and reintegrating them back with the build and running them on the
/llvm-project/llvm/utils/TableGen/Common/GlobalISel/
H A DCombinerUtils.h23 /// DagInit's support any type inside them.
34 /// DagInit's since DagInit's support any type inside them.
45 /// DagInit's support any type inside them.
59 /// similar in DagInit's since DagInit's support any type inside them.
/llvm-project/clang/include/clang/Basic/
H A DTokenKinds.def887 // handles them.
892 // handles them.
897 // handles them.
902 // handles them.
912 // handles them.
917 // handles them.
922 // handles them.
927 // handles them.
932 // handles them.
937 // handles them
[all...]
/llvm-project/lldb/docs/resources/
H A Dcaveats.rst27 them using a utility (such as ``pip``) from the same Python distribution as
50 Similarly, to install packages and be able to use them from within lldb, you'll
51 need to install them with the matching ``pip3``.
/llvm-project/bolt/include/bolt/Passes/
H A DValidateInternalCalls.h37 /// we just identify them, verify they are safe (do not reference objects
39 /// way they were read. We do this by marking them as non-simple.
41 /// Why do we freeze them?
48 /// non-canonical CFGs (specifically, fixBranches does not support them).
/llvm-project/llvm/lib/Support/Unix/
H A DDynamicLibrary.inc76 // If this is darwin, it has some funky issues, try to solve them here. Some
78 // SearchForAddressOfSymbol to find them. As such, we special case them here,
79 // there is only a small handful of them.
/llvm-project/lldb/test/API/tools/lldb-server/memory-tagging/
H A Dmain.c50 // ptrace expects you to remove them but it can still succeed if you in main()
51 // don't. So this isn't proof that we're removing them, it's just a in main()
52 // smoke test in case something didn't account for them. in main()

12345678910>>...168