Lines Matching refs:interfaces

9 operation type. To combat this, MLIR provides a concept of `interfaces`.
14 able to express transformations/analyses in terms of these interfaces without
22 Dialect interfaces are generally useful for transformation passes or analyses
24 may be defined in different dialects. These interfaces generally involve wide
38 using dialect-specific information. The interfaces defined by a dialect are
75 Once registered, these interfaces can be queried from the dialect by an analysis
114 Attribute/Operation/Type interfaces, as the names suggest, are those registered
115 at the level of a specific attribute/operation/type. These interfaces provide
123 These interfaces are defined by overriding the
213 implement interfaces for attributes, operations and types outside of the dialect
214 that defines them, for example, to provide interfaces for built-in types.
232   /// automatically generates this class for all interfaces.
263 External models can be provided for attribute, operation and type interfaces by
345 As detailed above, [Interfaces](#attributeoperationtype-interfaces) allow for
349 MLIR provides a mechanism with which to defines interfaces declaratively in ODS,
619 // Operation interfaces can optionally be wrapped inside
635 Note: Existing operation interfaces defined in C++ can be accessed in the ODS
640 MLIR includes standard interfaces providing functionality that is likely to be
641 common across many different operations. Below is a list of some key interfaces