Home
last modified time | relevance | path

Searched refs:ODS (Results 1 – 25 of 52) sorted by relevance

123

/llvm-project-15.0.7/mlir/test/mlir-linalg-ods-gen/
H A Dtest-linalg-ods-yaml-gen.yaml65 # ODS: let summary = [{ Title. }];
66 # ODS-NEXT: let description = [{
67 # ODS-NEXT: Detailed description.
68 # ODS-NEXT: }];
70 # ODS: let arguments =
71 # ODS-NEXT: Variadic<AnyType>:$inputs,
75 # ODS: let builders =
77 # ODS-NEXT: "ValueRange":$outputs,
157 # ODS: let arguments =
163 # ODS: "Attribute":$strides
[all …]
/llvm-project-15.0.7/mlir/test/mlir-tblgen/
H A Dllvm-intrinsics.td2 // files and produce ODS. Unlike MLIR, LLVM's main Intrinsics.td file that
80 // This checks that the ODS we produce can be consumed by MLIR tablegen. We only
82 // of this C++ code is tested by ODS tests.
88 // RUN: | FileCheck --check-prefix=ODS %s
90 // ODS-LABEL: class vastart
/llvm-project-15.0.7/mlir/test/mlir-pdll-lsp-server/
H A Dsignature-help.test22 // CHECK-NEXT: "documentation": "`op<test.multi>` ODS operand specification",
68 // CHECK-NEXT: "documentation": "`op<test.multi>` ODS operand specification",
101 // CHECK-NEXT: "documentation": "`op<test.multi>` ODS result specification",
147 // CHECK-NEXT: "documentation": "`op<test.multi>` ODS result specification",
/llvm-project-15.0.7/mlir/lib/Tools/PDLL/
H A DCMakeLists.txt3 add_subdirectory(ODS)
/llvm-project-15.0.7/mlir/include/mlir/Dialect/Linalg/IR/
H A DCMakeLists.txt1 # Declare a function to generate ODS with mlir-linalg-ods-yaml-gen
38 # include Linalg in ODS
/llvm-project-15.0.7/mlir/docs/Dialects/
H A D_index.md6 [Operation Definition Specification (ODS)](../OpDefinitions.md).
/llvm-project-15.0.7/mlir/docs/Tutorials/
H A DCreatingADialect.md13 TableGen file in the [ODS format](../OpDefinitions.md), describing the
20 the dialect which are not automatically generated by ODS. These are
36 Operations in dialects are typically declared using the ODS format in
/llvm-project-15.0.7/mlir/include/mlir/IR/
H A DDialectBase.td77 // When set, ODS will generate declarations for the attribute parsing and
83 // When set, ODS will generate declarations for the type parsing and printing
/llvm-project-15.0.7/mlir/include/mlir/Interfaces/
H A DDerivedAttributeOpInterface.td23 from information of the operation. ODS generates convenience accessors for
H A DInferIntRangeInterface.td43 `argRanges` contains one `IntRangeAttrs` for each argument to the op in ODS
/llvm-project-15.0.7/mlir/include/mlir/Bindings/Python/
H A DAttributes.td9 // This defines the mapping between MLIR ODS attributes and the corresponding
/llvm-project-15.0.7/mlir/docs/
H A DInterfaces.md231 /// defined in the class itself and thus has no `this` access. ODS
251 /// lead to compilation errors. ODS automatically generates this class and
308 A second model is used for such cases and automatically generated when using ODS
339 #### Utilizing the ODS Framework
349 MLIR provides a mechanism with which to defines interfaces declaratively in ODS,
352 As an example, using the ODS framework would allow for defining the example
456 ODS also allows for generating declarations for the `InterfaceMethod`s of an
635 Note: Existing operation interfaces defined in C++ can be accessed in the ODS
646 - (`C++ class` -- `ODS class`(if applicable))
H A DCanonicalization.md70 In [ODS](OpDefinitions.md), an operation can set the `hasCanonicalizer` bit or
120 In [ODS](OpDefinitions.md), an operation can set the `hasFolder` bit to generate
203 In [ODS](DefiningDialects.md), a dialect can set the `hasConstantMaterializer` bit
H A DPDLL.md9 [Operation Definition Specification (ODS)](https://mlir.llvm.org/docs/OpDefinitions/)
260 [ODS](https://mlir.llvm.org/docs/OpDefinitions/) information within that file.
262 them implicitly accessible within PDLL. This is important, as ODS information
598 defined on the operation in ODS.
600 Given the following operation definition in ODS:
635 defined on the operation in ODS.
637 Given the following operation definition in ODS:
763 Given the following operation definition in ODS:
786 `Value` or `ValueRange`. If these variables are registered (has ODS entry), they
1197 // `my_ops.td` provides the ODS definition of the `my_dialect` operations, such as
[all …]
H A DDeclarativeRewrites.md5 [Op Definition Specification](OpDefinitions.md) (ODS), this is achieved via
18 manual assumes knowledge of the [ODS](OpDefinitions.md) doc.
141 the ODS name directly in the pattern is also allowed. Operands in the source
244 the pattern by following the exact same order as the ODS `arguments` definition.
247 Right now all ODS-generated `build()` methods require specifying the result
251 matched root op's result type when calling the ODS-generated builder. Otherwise
255 type deduction ability via `OpBuilder` in ODS. For example, in the following
616 in ODS of the op
H A DOpDefinitions.md1 # Operation Definition Specification (ODS)
445 ODS will generate a builder that doesn't require the return type specified if
474 declarations in ODS, which use a TableGen [`dag`](#tablegen-syntax). What
496 Implementations of the builder can be provided directly in ODS, using TableGen
516 inline in ODS and put definitions of longer builders in C++ files.
585 2. `verifyInvariants` which is constructed by ODS, it verifies the type,
973 directly buildable; for example the `I32` or `Index` types. Types in `ODS` may
1257 ODS provides attribute wrappers over C++ attribute classes. There are a few
1273 applied to ODS attributes to specify common additional properties like
1285 comparison kind of a comparison op. To define such attributes, ODS provides
[all …]
H A DTraits.md140 ### Attaching Operation Traits in ODS
142 To use an operation trait in the [ODS](OpDefinitions.md) framework, we need to
193 - (`C++ class` -- `ODS class`(if applicable))
/llvm-project-15.0.7/mlir/include/mlir/Dialect/PDL/IR/
H A DPDLOps.td297 defined on the operation in ODS.
300 // Given the following operation definition in ODS:
327 defined on the operation in ODS.
330 // Given the following operation definition in ODS:
490 as defined by the ODS definition of the operation.
521 a result group as defined by the ODS definition of the operation. In this
523 a `pdl.range<value>`, depending on the constraint of the result in ODS. If
/llvm-project-15.0.7/mlir/docs/Tutorials/Toy/
H A DCh-2.md190 // Provide a definition of the 'toy' dialect in the ODS framework so that we
350 ### Using the Operation Definition Specification (ODS) Framework
357 compile time. Using the ODS framework is the desired way for defining operations
361 Lets see how to define the ODS equivalent of our ConstantOp:
363 Operations in ODS are defined by inheriting from the `Op` class. To simplify our
426 By providing a name to the arguments or results, e.g. `$value`, ODS will
467 named accessor, the ODS framework will automatically generate a lot of the
471 necessary for ODS operations. To add additional verification logic, an operation
501 // operation class that is called after ODS constructs have been verified, for
511 methods. ODS can generate some simple build methods automatically, and in this
[all …]
H A DCh-7.md195 ### Exposing to ODS
197 After defining a new type, we should make the ODS framework aware of our Type so
202 // Provide a definition for the Toy StructType for use in ODS. This allows for
220 exposed to ODS as detailed in the previous section.
H A DCh-5.md132 // by the ODS. This adaptor is automatically provided by the ODS
204 the first. Defining a base class in [ODS](../../OpDefinitions.md) may
/llvm-project-15.0.7/mlir/test/mlir-pdll/Parser/
H A Dexpr-failure.pdll304 // CHECK-SAME: Include the ODS definition of this operation to remove this
320 // CHECK-SAME: to the ODS definition to remove this warning.
/llvm-project-15.0.7/mlir/test/python/
H A Dpython_test_ops.td87 // autogenerated by C++ ODS.
/llvm-project-15.0.7/mlir/test/lib/Dialect/Test/
H A DTestInterfaces.td15 // A type interface used to test the ODS generation of type interfaces.
/llvm-project-15.0.7/clang/lib/Sema/
H A DSemaObjCProperty.cpp175 ObjCDeclSpec &ODS, in ActOnProperty() argument
180 unsigned Attributes = ODS.getPropertyAttributes(); in ActOnProperty()
199 GetterSel, ODS.getGetterNameLoc(), in ActOnProperty()
200 SetterSel, ODS.getSetterNameLoc(), in ActOnProperty()
202 ODS.getPropertyAttributes(), in ActOnProperty()
211 GetterSel, ODS.getGetterNameLoc(), SetterSel, in ActOnProperty()
212 ODS.getSetterNameLoc(), isReadWrite, Attributes, in ActOnProperty()
213 ODS.getPropertyAttributes(), T, TSI, in ActOnProperty()

123