Home
last modified time | relevance | path

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

12

/external/llvm-project/mlir/test/mlir-linalg-ods-gen/
Dtest-linalg-ods-gen.tc1 // RUN: mlir-linalg-ods-gen %s -gen-ods-decl=1 | FileCheck %s --check-prefix=ODS
4 // ODS-LABEL: def Test1Op : LinalgStructuredBase_Op<"test1", [
5 // ODS-NEXT: AttrSizedOperandSegments
6 // ODS-NEXT: DeclareOpInterfaceMethods<MemoryEffectsOpInterface>,
7 // ODS-NEXT: NamedStructuredOpTrait
8 // ODS-NEXT: SingleBlockImplicitTerminator<"YieldOp">
29 // ODS-LABEL: def Test2Op : LinalgStructuredBase_Op<"test2", [
30 // ODS-NEXT: AttrSizedOperandSegments
31 // ODS-NEXT: DeclareOpInterfaceMethods<MemoryEffectsOpInterface>,
32 // ODS-NEXT: NamedStructuredOpTrait
[all …]
/external/llvm-project/mlir/test/mlir-tblgen/
Dllvm-intrinsics.td2 // files and produce ODS. Unlike MLIR, LLVM's main Intrinsics.td file that
31 // This checks that the ODS we produce can be consumed by MLIR tablegen. We only
33 // of this C++ code is tested by ODS tests.
39 // RUN: | FileCheck --check-prefix=ODS %s
41 // ODS-LABEL: class vastart
/external/llvm-project/mlir/include/mlir/Dialect/Linalg/IR/
DCMakeLists.txt1 # Declare a function to generate ODS with mlir-linalg-ods-gen
30 # include Linalg in ODS
/external/tensorflow/tensorflow/compiler/mlir/tensorflow/ir/
Dtf_op_base.td454 // A derived attribute that returns the size of `idx`-th ODS-declared variadic
462 // A derived attribute that returns the element type of `idx`-th ODS-declared
471 // actual value pack that corresponds to the `idx`-th ODS-declared variadic
491 // value pack that corresponds to the `idx`-th ODS-declared variadic operand.
510 // A derived attribute that returns the size of `idx`-th ODS-declared variadic
518 // A derived attribute that returns the element type of `idx`-th ODS-declared
527 // actual value pack that corresponds to the `idx`-th ODS-declared variadic
547 // value pack that corresponds to the `idx`-th ODS-declared variadic result.
/external/llvm-project/mlir/docs/Tutorials/
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
/external/llvm-project/mlir/docs/
DInterfaces.md182 #### Utilizing the ODS Framework
185 together. The ODS(Operation Definition Specification) framework provides
188 As an example, using the ODS framework would allow for defining the example
214 - (`C++ class` -- `ODS class`(if applicable))
DCanonicalization.md70 In [ODS](OpDefinitions.md), an operation can set the `hasCanonicalizer` bit to
106 In [ODS](OpDefinitions.md), an operation can set the `hasFolder` bit to generate
188 In [ODS](OpDefinitions.md), a dialect can set the `hasConstantMaterializer` bit
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 the matched root op's result type when calling the ODS-generated builder.
255 that has result type deduction ability via `OpBuilder` in ODS. For example,
584 in ODS of the op
DOpDefinitions.md1 # Operation Definition Specification (ODS)
353 accessed in the ODS framework via the `OpInterfaceTrait` class. Aside from using
354 pre-existing interfaces in the C++ API, the ODS framework also provides a
400 ODS also allows generating the declarations for the `InterfaceMethod` of the op
556 ODS will generate a builder that doesn't require return type specified if
585 declarations in ODS, which use a TableGen [`dag`](#tablegen-syntax). What
607 Implementations of the builder can be provided directly in ODS, using TableGen
627 inline in ODS and put definitions of longer builders in C++ files.
972 be directly buildable; for example the `I32` or `Index` types. Types in `ODS`
1234 ODS provides attribute wrappers over C++ attribute classes. There are a few
[all …]
DTraits.md137 ### Attaching Operation Traits in ODS
139 To use an operation trait in the [ODS](OpDefinitions.md) framework, we need to
190 - (`C++ class` -- `ODS class`(if applicable))
DShapeInference.md242 #### What about ODS specifications of operations?
244 In ODS we have been recording the constraints for the operands & attributes of
/external/llvm-project/mlir/include/mlir/Interfaces/
DDerivedAttributeOpInterface.td23 from information of the operation. ODS generates convenience accessors for
/external/llvm-project/mlir/include/mlir/Bindings/Python/
DAttributes.td9 // This defines the mapping between MLIR ODS attributes and the corresponding
/external/llvm-project/mlir/test/lib/Dialect/Test/
DTestInterfaces.td15 // A type interface used to test the ODS generation of type interfaces.
/external/llvm-project/mlir/docs/Tutorials/Toy/
DCh-2.md299 ### Using the Operation Definition Specification (ODS) Framework
306 compile time. Using the ODS framework is the desired way for defining operations
310 Lets see how to define the ODS equivalent of our ConstantOp:
317 // Provide a definition of the 'toy' dialect in the ODS framework so that we
330 operations. Operations in ODS are defined by inheriting from the `Op` class. To
393 By providing a name to the arguments or results, e.g. `$value`, ODS will
434 named accessor, the ODS framework will automatically generate a lot of the
438 necessary for ODS operations. To add additional verification logic, an operation
477 methods. ODS can generate some simple build methods automatically, and in this
678 Above we introduce several of the concepts for defining operations in the ODS
DCh-5.md125 // by the ODS. This adaptor is automatically provided by the ODS
198 Defining a base class in [ODS](../../OpDefinitions.md) may simplify this, but
DCh-4.md264 the operation definition specification (ODS) framework.
284 [ODS documentation](../../OpDefinitions.md#operation-interfaces) for more
/external/curl/packages/vms/
Dbuild_gnv_curl_pcsi_desc.com9 $! 2. ODS-5 filenames need an alias procedure. (N/A for curl)
24 $! The PCSI system can really only handle ODS-2 format filenames and
149 $! 2. ODS-5 filenames need an alias procedure. (N/A for curl)
Dcurl_gnv_build_steps.txt42 an ODS-5 volume(s) which are referenced by concealed rooted logical names.
226 to the kit. These files should all be ODS-2 legal filenames and
238 While newer versions of PCSI can support ODS-5 filenames, not all versions
239 of PCSI on systems that have ODS-5 filenames do. So as a post install
Dbackup_gnv_curl_src.com11 $! VMS system to be able to extract ODS-5 filenames and directories.
Dcompare_curl_source.com31 $! This needs to be run on an ODS-5 volume.
/external/llvm-project/clang/lib/Sema/
DSemaObjCProperty.cpp177 ObjCDeclSpec &ODS, in ActOnProperty() argument
182 unsigned Attributes = ODS.getPropertyAttributes(); in ActOnProperty()
201 GetterSel, ODS.getGetterNameLoc(), in ActOnProperty()
202 SetterSel, ODS.getSetterNameLoc(), in ActOnProperty()
204 ODS.getPropertyAttributes(), in ActOnProperty()
213 GetterSel, ODS.getGetterNameLoc(), SetterSel, in ActOnProperty()
214 ODS.getSetterNameLoc(), isReadWrite, Attributes, in ActOnProperty()
215 ODS.getPropertyAttributes(), T, TSI, in ActOnProperty()
/external/llvm-project/mlir/examples/toy/Ch7/include/toy/
DOps.td20 // Provide a definition of the 'toy' dialect in the ODS framework so that we
35 // Provide a definition for the Toy StructType for use in ODS. This allows for
/external/llvm-project/mlir/examples/toy/Ch2/include/toy/
DOps.td19 // Provide a definition of the 'toy' dialect in the ODS framework so that we
/external/llvm-project/mlir/examples/toy/Ch3/include/toy/
DOps.td18 // Provide a definition of the 'toy' dialect in the ODS framework so that we

12