Home
last modified time | relevance | path

Searched refs:relationship (Results 1 – 25 of 38) sorted by relevance

12

/llvm-project-15.0.7/third-party/benchmark/test/
H A Doutput_test.h159 #define CHECK_RESULT_VALUE_IMPL(entry, getfn, var_type, var_name, relationship, value) \ argument
160 CONCAT(BM_CHECK_, relationship) \
166 << " to be " #relationship " to " << (value) << "\n"
171 CONCAT(BM_CHECK_FLOAT_, relationship) \
177 << " to be " #relationship " to " << (value) << "\n" \
187 #define CHECK_RESULT_VALUE(entry, var_type, var_name, relationship, value) \ argument
188 CHECK_RESULT_VALUE_IMPL(entry, GetAs, var_type, var_name, relationship, value)
190 #define CHECK_COUNTER_VALUE(entry, var_type, var_name, relationship, value) \ argument
191 CHECK_RESULT_VALUE_IMPL(entry, GetCounterAs, var_type, var_name, relationship, value)
193 #define CHECK_FLOAT_RESULT_VALUE(entry, var_name, relationship, value, eps_factor) \ argument
[all …]
/llvm-project-15.0.7/llvm/docs/
H A DHowToUseInstrMappings.rst24 TableGen uses relationship models to map instructions with each other. These
42 // by all the instructions related by this relationship.
67 to define a relationship model that relates predicated instructions to their
69 fields. For this relationship, non-predicated instructions are treated as key
76 // instructions modeling this relationship. This is done to reduce the
96 // instructions involved in this relationship model.
107 TableGen uses the above relationship model to emit relation table that maps
137 required by the relationship model, <tt>getPredOpcode</tt>, so that they can
H A DInstrRefDebugInfo.md32 instruction. Instruction referencing implements this relationship in the
H A DSupportLibrary.rst100 There must **not** be a one-to-one relationship between operating system
H A DGarbageCollection.rst150 specified by the *runtime library*. This is similar to the relationship between
342 LLVM does not enforce this relationship between the object and derived pointer
H A DHowToUpdateDebugInfo.rst135 relationship to a source location.
H A DExceptionHandling.rst716 parent relationship is encoded in the IR using tokens produced by the new "pad"
785 funclet nesting relationship to encode unwind destinations, and so are
/llvm-project-15.0.7/llvm/test/CodeGen/AArch64/
H A Dtailcall_misched_graph.ll31 ; dependency relationship still holds.
48 ; GlobalISel outputs DEPSTOREB before DEPSTOREA, but the dependency relationship
H A Dmachine-copy-prop.ll10 ; remove the relationship of D6 and "%q5_q6 = COPY %q2_q3".
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/readability/
H A Dstring-compare.rst11 zero depending on the lexicographical relationship between the strings compared.
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines/
H A Dspecial-member-functions.rst11 suppressed by explicit user-definitions. The relationship between which
/llvm-project-15.0.7/llvm/test/CodeGen/PowerPC/
H A Dasym-regclass-copy.ll5 ; This tests that the GPRC/GPRC_NOR0 intersection subclass relationship with
/llvm-project-15.0.7/mlir/include/mlir/Dialect/Tosa/IR/
H A DTosaOpBase.td77 // the operator has a numerical relationship between a single input and output.
180 // relationship between their input and output, expressed by the
/llvm-project-15.0.7/mlir/test/Analysis/
H A Dtest-dominance.mlir208 // CHECK-LABEL: --- Block Dominance relationship ---
258 // CHECK-LABEL: --- Block PostDominance relationship ---
/llvm-project-15.0.7/llvm/test/Other/
H A Dcgscc-observe-devirt.ll60 ; introduces a new post-order relationship that was not present originally and
/llvm-project-15.0.7/llvm/test/Transforms/SCCP/
H A Dmetadata.ll71 ; There is no particular relationship between two nonnull values.
/llvm-project-15.0.7/llvm/docs/DependenceGraphs/
H A Dindex.rst73 node and edge types resulting in the inheritance relationship depicted
/llvm-project-15.0.7/llvm/test/Transforms/InstCombine/
H A Dcast_ptr.ll9 ; This shouldn't convert to getelementptr because the relationship
/llvm-project-15.0.7/mlir/docs/
H A DDeclarativeRewrites.md101 the def-use relationship between ops.
485 relationship can be expressed in the way that an op's result can feed as the
701 best location mapping relationship. For such cases, DRR provides the `location`
/llvm-project-15.0.7/mlir/docs/Tutorials/
H A DUnderstandingTheIRStructure.md218 Another relationship in the IR is the one that links a `Value` with its users.
/llvm-project-15.0.7/llvm/bindings/ocaml/debuginfo/
H A Dllvm_debuginfo.mli515 to establish inheritance relationship between two types.
/llvm-project-15.0.7/llvm/test/CodeGen/WebAssembly/
H A Dcfg-stackify-eh.ll1444 ; (> here represents subexception relationship)
1447 ; catch.start12. So all these subexception relationship should be deconstructed.
1450 ; catch.start4's exception; otherwise we end up with an incorrect relationship
/llvm-project-15.0.7/llvm/include/llvm/Target/
H A DTarget.td677 /// The relationship and helper function generation are handled by
1727 // define the relationship modeled by this InstrMapping record.
1732 // properties shared by all the instructions related by this relationship
/llvm-project-15.0.7/mlir/docs/Dialects/
H A DVector.md256 The relationship with the LLVM Matrix proposal is discussed at the end of this
/llvm-project-15.0.7/mlir/docs/Rationale/
H A DMLIRForGraphAlgorithms.md20 MLIR's relationship to XLA, Eigen, etc, are out of scope for this particular

12