Lines Matching refs:operations

33 [type system](#type-system). [Operations](#operations) are contained in
44 gates. These different concepts are represented by different operations in MLIR
45 and the set of operations usable in MLIR can be arbitrarily extended.
47 MLIR also provides an extensible framework for transformations on operations,
49 set of passes on an arbitrary set of operations results in a significant scaling
53 [Interfaces](Interfaces.md), enabling transformations to operate on operations
56 [Op vs Operation](Tutorials/Toy/Ch-2.md/#op-vs-operation-using-mlir-operations))
190 consuming the MLIR syntax. [Operations](#operations),
230 body. Particular operations may further limit which identifiers are in scope in
245 ecosystem. They allow for defining new [operations](#operations), as well as
265 ### Target specific operations
268 operations directly through to MLIR. As an example, some targets go through
270 operations (e.g. addition with overflow check) as well as providing access to
271 target-specific operations for the targets it supports (e.g. vector permutation
272 operations). LLVM intrinsics in MLIR are represented via operations that start
282 These operations only work when targeting LLVM as a backend (e.g. for CPUs and
304 MLIR introduces a uniform concept called *operations* to enable describing many
306 extensible (there is no fixed list of operations) and have application-specific
308 [target-independent operations](Dialects/MemRef.md),
309 [affine operations](Dialects/Affine.md), and
310 [target-specific machine operations](#target-specific-operations).
335 In addition to the basic syntax above, dialects may register known operations.
337 printing operations. In the operation sets listed below, we show both forms.
341 The [builtin dialect](Dialects/Builtin.md) defines a select few operations that
363 A *Block* is a list of operations. In
366 instructions inside the block are executed in order and terminator operations
377 operations. Block arguments of the entry block of a region are also arguments to
380 determined by the semantics of terminator operations, e.g. Branches, which have
417 cases from the IR compared to traditional "PHI nodes are operations" SSA IRs
423 are also a fundamental concept that cannot be represented by operations because
439 do. Regions must be contained within operations and have no type or attributes.
456 general, operations with regions can define these correspondences arbitrarily.
469 the enclosing region, if any. By default, operations inside a region can
498 regions support semantics where operations in a region 'execute sequentially'.
509 of the region, called the *entry* block. Terminator operations ending each block
513 operation. Terminator operations without successors can only pass control back
515 of terminator operations is determined by the specific dialect operations
522 standard dialect leverages this capability to define operations with
564 other operations, in particular those that defined the values or symbols the
585 fundamental order to the relationships. For instance, operations in a graph
598 In graph regions, MLIR operations naturally represent nodes, while each MLIR
600 destination nodes. All values defined in the region as results of operations are
602 region. In graph regions, the order of operations within a block and the order
604 operations may be freely reordered, for instance, by canonicalization. Other
607 operations.
682 Similarly to operations, dialects may define custom extensions to the type
745 Attributes are the mechanism for specifying constant data on operations in
765     itself, but must be compatible with the operations's semantics. These
801 Similarly to operations, dialects may define custom attribute values.