Home
last modified time | relevance | path

Searched refs:like (Results 1 – 25 of 1099) sorted by relevance

12345678910>>...44

/llvm-project-15.0.7/mlir/include/mlir/Interfaces/
H A DCallInterfaces.td10 // related to call-like and callable operations. Each of which are defined along
22 // a call-like operation. This represents the destination of the call.
24 /// Interface for call-like operations.
27 A call-like operation is one that transfers control from one sub-routine to
36 Returns the callee of this call-like operation. A `callee` is either a
39 to a region of a lambda-like operation.
65 be a target for a call-like operation (those providing the CallOpInterface
H A DCastInterfaces.td10 // related to cast-like operations.
21 A cast-like operation is one that converts from a set of input types to a
23 arity of the outputs may be anything from 1-N. Cast-like operations are
H A DCopyOpInterface.td9 // Defines the interface for copy-like operations.
20 A copy-like operation is one that copies from source value to target value.
/llvm-project-15.0.7/mlir/test/Dialect/Arithmetic/
H A Dinvalid.mlir107 // expected-error@+1 {{'arith.addi' op operand #0 must be signless-integer-like}}
152 // Result type must be boolean like.
178 // expected-error@+1 {{'lhs' must be signless-integer-like, but got '() -> ()'}}
231 %r = arith.cmpf oeq, %a, %b : i32 // expected-error {{must be floating-point-like}}
237 // expected-error@+1 {{result #0 must be bool-like}}
304 // expected-error@+1 {{op result #0 must be floating-point-like, but got 'i64'}}
336 // expected-error@+1 {{op operand #0 must be floating-point-like, but got 'i32'}}
344 // expected-error@+1 {{op result #0 must be floating-point-like, but got 'i32'}}
384 // expected-error@+1 {{op result #0 must be floating-point-like, but got 'vector<2xi32>'}}
408 // expected-error@+1 {{op operand #0 must be floating-point-like, but got 'i32'}}
[all …]
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/abseil/
H A Dstring-find-str-contains.rst6 Finds ``s.find(...) == string::npos`` comparisons (for various string-like types)
10 ``find()`` and ``npos`` from different string-like types.
12 By default, "string-like types" includes ``::std::basic_string``,
40 Semicolon-separated list of names of string-like classes. By default includes
/llvm-project-15.0.7/llvm/docs/HistoricalNotes/
H A D2001-01-31-UniversalIRIdea.txt12 (some low-level like standard assembly instructions with code generation and
13 static and runtime optimization; some higher-level like type-safety and
17 features as well as low-level machine-independent optimizations (like PRE)
21 machine-independent features like type-safety and access safety should be
25 The risk is that this sounds like a universal IR -- something that the
H A D2001-02-09-AdveCommentsResponse.txt31 > On reflection, I really like your idea of having the two different
62 + You NEED casts to represent things like:
68 in a language like C. Even in a Java like language, you need upcasts
107 pointers like the builtin function would) if one is available, otherwise
110 Does this sound like a good compromise? It would give us all of the
114 > 'alloca' on the other hand sounds like a good idea, and the
132 that they want languages like Haskell and lisp to be efficiently runnable
155 tend to prefer that a predicated architecture like IA64 convert from a
173 Basically, the IA64 writes instructions like this:
226 constants with [] brackets as in my syntax, which would look like this:
H A D2002-05-12-InstListChange.txt6 There is a fairly fundemental change that I would like to make to the LLVM
7 infrastructure, but I'd like to know if you see any drawbacks that I
19 instruction! This complicates algorithms that should be very simple (like
28 To fix these problems (and others), I would like to make the ordering of
H A D2001-02-13-Reference-Memory.txt13 I have a couple of concerns I would like to bring up:
19 subtracted, moved, etc... Do we want to have a type like this? It
22 pointer type would be kept for C++ like semantics. Through analysis,
/llvm-project-15.0.7/libc/docs/
H A Druntimes_build.rst5 various runtimes (like ``libc++`` and ``compiler-rt``) and LLVM binutils (like
34 parts and to also generate the public headers. Likewise, we would like to
35 provide an option to build other runtimes like ``libc++`` and ``compiler-rt``
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/bugprone/
H A Dstring-literal-with-embedded-nul.rst13 hexadecimal encoding like ``\x42``. A common mistake is to escape them
14 like this ``\0x42`` where the ``\0`` stands for the NUL character.
24 String-like classes can manipulate strings with embedded NUL as they are keeping
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/modernize/
H A Duse-emplace.rst18 This check also reports when an ``emplace``-like method is improperly used,
21 ``emplace``-like functions in the STL are covered by this, with ``try_emplace``
25 ``value_type`` type, and the ``emplace``-like functions construct a
57 ``std::pair`` and ``std::tuple``. Custom tuple-like types can be modified by
137 Semicolon-separated list of ``std::tuple``-like class names.
141 Semicolon-separated list of ``std::make_tuple``-like function names. Those
148 and some ``emplace``-like method of the container. Example:
/llvm-project-15.0.7/llvm/docs/
H A DMarkdownQuickstartTemplate.md42 like the other "how to" documents. This format is usually the easiest
62 Headings (like `Example Section` just above) give your document its
67 Make a link [like this](https://llvm.org/). There is also a more
74 Lists can be made like this:
92 You can make blocks of code like this:
132 without any syntax highlighting like this:
H A DHowToSetUpLLVMStyleRTTI.rst96 it, like "opcode". Don't bikeshed over this; when in doubt use ``Kind``.
212 check roughly like ``Circle::classof(S)``. For more information, see
218 ``Foo`` automatically has a ``classof`` like:
269 Then in ``Square``, we would need to modify the ``classof`` like so:
289 list the class hierarchy like a list of bullet points, you'll get the
306 a subclass of ``Square``, and update the ``ShapeKind`` enum like so:
319 looks like:
396 Touch on some of the more advanced features, like ``isa_impl`` and
510 we can use some provided cast traits like so:
548 In those cases, you probably want something like this:
[all …]
/llvm-project-15.0.7/llvm/test/tools/llvm-symbolizer/
H A Dsplit-dwarf.test10 Ensure we get the same results in the absence of gmlt-like data in the executable but the presence …
17 Ensure we get gmlt like results in the absence of a .dwo file but the presence of gmlt-like data in…
/llvm-project-15.0.7/mlir/docs/Rationale/
H A DUsageOfConst.md14 about this. That said, you *should* use `const` for non-IR types, like
21 Bjarke Roune summarized the situation like this:
42 **Note:** This document is only discussing things like `const Value` and
44 `SmallVector` references, the immutable types like `Attribute`, etc.
48 The LLVM and MLIR data structures provide the IR data structures (like
59 like this:
103 passed in - similarly predicates like `Instruction::isTerminator() const` do not
165 otherwise be desirable. Things like `ResultIterator` and `ResultTypeIterator`
186 cloning methods are defined on `Operation` like this:
202 The "typed operation" classes for registered operations (e.g. like `DimOp` for
[all …]
H A DRationaleGenericDAGRewriter.md19 compilers and necessary for peephole optimizations like "eliminate identity
25 infrastructures like LLVM, GCC, XLA, TensorFlow, etc) is that it uses a single
35 (SSA) representations like MLIR make it easy to access the operands and "users"
70 usually, narrow problem: MLIR on the other hand would like to solve many of
161 In addition to structured "combiners" like these, there are lots of ad-hoc
162 systems like the
177 writing patterns like this.
189 entangled in details of the compiler like assembler/disassembler generation
196 * It automates matching across identities, like commutative patterns.
231 We'd like the to encompass many problems in the MLIR space, including 1-to-N
[all …]
/llvm-project-15.0.7/mlir/include/mlir/Dialect/Tosa/IR/
H A DTosaTypesBase.td157 def Tosa_IntLike : Tosa_TypeLike<[Tosa_Int], "signless-integer-like">;
158 def Tosa_Int8Like : Tosa_TypeLike<[Tosa_Int8], "signless-integer-8-bit-like">;
159 def Tosa_Int16Like : Tosa_TypeLike<[Tosa_Int16], "signless-integer-16-bit-like">;
160 def Tosa_Int32Like : Tosa_TypeLike<[Tosa_Int32], "signless-integer-32-bit-like">;
161 def Tosa_Int64Like : Tosa_TypeLike<[Tosa_Int64], "signless-integer-64-bit-like">;
/llvm-project-15.0.7/llvm/test/Transforms/GlobalDCE/
H A Dcrash-assertingvh.ll1 ; Make sure that if a pass like jump threading populates a function analysis
2 ; like LVI with asserting handles into the body of a function, those don't begin
/llvm-project-15.0.7/clang/test/SemaObjC/
H A Dattr-called-once.m5 …LED_ONCE); // expected-error{{'called_once' attribute only applies to function-like parameters}}
6 …CALLED_ONCE); // expected-error{{'called_once' attribute only applies to function-like parameters}}
/llvm-project-15.0.7/llvm/test/CodeGen/X86/
H A Dcoalescer-subreg.ll2 ; This used to crash when coalescing a regclass like GR16 which did not support
3 ; the sub_8bit_hi subregister with a class like GR16_ABCD that did.
/llvm-project-15.0.7/clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines/
H A Downing-memory.rst7 static analysis on code, that uses raw pointers to handle resources like
24 ``malloc()``-like resource functions are considered to produce resources.
111 In template functions and classes, like in the example below, the information
145 // The same issue occurs with templated classes like the following.
160 Suppose you have code like the following:
171 The semantic of a ``gsl::owner<T*>`` is mostly like a ``std::unique_ptr<T>``, therefore
/llvm-project-15.0.7/clang/docs/
H A DCrossCompilation.rst46 Another problem is that compilers come with standard libraries only (like
53 option will work magically. Some options, like ``--sysroot`` (which
93 like the bare-metal "none".
97 that Clang doesn't know, like ``blerg``, it'll ignore and assume
112 * ``-mcpu=<cpu-name>``, like x86-64, swift, cortex-a15
113 * ``-mfpu=<fpu-name>``, like SSE3, NEON, controlling the FP unit available
114 * ``-mfloat-abi=<fabi>``, like soft, hard, controlling which registers
167 normally checked against (like ``libxml`` or ``libz`` etc) will match
201 The same is true if you're compiling for different ABIs, like ``gnueabi``
/llvm-project-15.0.7/libc/test/integration/loader/
H A DCMakeLists.txt3 # while the loader is getting built, we need to use a special rule like
9 "Loader tests currently assume a POSIX/Unix like environment and "
/llvm-project-15.0.7/libc/utils/UnitTest/
H A DREADME.md4 [gtest](https://github.com/google/googletest) like unit test framework for LLVM
17 But, what is available strives to be exactly like gtest.

12345678910>>...44