Lines Matching refs:OpView

377 -   a specific subclass of `OpView` that provides more semantically-loaded
380 Given an `OpView` subclass, one can obtain an `Operation` using its `.operation`
381 property. Given an `Operation`, one can obtain the corresponding `OpView` using
384 default, the `OpView` version is produced when navigating the IR tree.
421 `OpView` subclasses for specific operations may provide leaner accessors to
423 are usually accessible as properties of the `OpView` subclass with the same
546 -   an object of the `Operation` class or of any `OpView` subclass; in this
548 -   a subclass of `OpView` and a context; in this case, only the *static*
571   # or an OpView.
574   # An interface object can also be constructed given an OpView subclass. It
594 If an interface object was constructed from an `Operation` or an `OpView`, they
612 `OpView` subclasses. The generic, default form of the constructor accepts:
651 constructor for `OpView`. *This form is discouraged* from use and is intended
666     # The result will be downcasted to the concrete `OpView` subclass if
696 `OpView` subclasses to provide a `.body` property that can be used to construct
933 *   An `{OpName}` class for each operation (extending `mlir.ir.OpView`).
939 Each concrete `OpView` subclass further defines several public-intended
952 on `OpView`):
961     variadics. Used by `OpView._ods_build_default` to decode operand and result
985 In addition, each `OpView` inherits a `build_generic` method which allows
1017 Then for each generated concrete `OpView` subclass, it will apply a decorator
1023 class FuncOp(_ods_ir.OpView):
1042 ordering, the mixin class can act as though it extends the generated `OpView`
1043 subclass in most contexts (i.e. `issubclass(_builtin_ops_ext.FuncOp, OpView)`
1045 `OpView`).
1055     actually want to invoke the super-super-class `mlir.ir.OpView` constructor
1068     OpView.__init__(self, self.build_generic(