Lines Matching defs:Operations

35 In MLIR, [`Operations`](../../LangRef.md/#operations) are the core unit of
37 Operations can have application-specific semantics and can be used to represent
87 the set of operations in MLIR is extensible. Operations are modeled
232 ## Defining Toy Operations
280   /// Operations may provide additional verification beyond what the attached
313 ### Op vs Operation: Using MLIR Operations
354 [Operation Definition Specification](../../DefiningDialects/Operations.md) framework. Facts
363 Operations in ODS are defined by inheriting from the `Op` class. To simplify our
382 [mnemonic](../../DefiningDialects/Operations.md/#operation-name) here matches the one given in
408 [inputs](../../DefiningDialects/Operations.md/#operation-arguments) and
409 [outputs](../../DefiningDialects/Operations.md/#operation-results) to our operation. The
432 The next step after defining the operation is to document it. Operations may
434 [`summary` and `description`](../../DefiningDialects/Operations.md/#operation-documentation)
472 can override the [`verifier`](../../DefiningDialects/Operations.md/#custom-verifier-code)
513 [`builders`](../../DefiningDialects/Operations.md/#custom-builder-methods) field. This field
586 [declaratively](../../DefiningDialects/Operations.md/#declarative-assembly-format) or
658 [declarative format](../../DefiningDialects/Operations.md/#declarative-assembly-format). The
684 The [declarative format](../../DefiningDialects/Operations.md/#declarative-assembly-format) has
713 [full specification](../../DefiningDialects/Operations.md) for more details.