Lines Matching defs:dialect

118 *   `mlir.dialect`
125 included "in the box" and covers things like dialect registration, pass
151 Especially for the core, dialect-independent parts, such a binding enables
383 This typically means that the Python module of its dialect has been loaded. By
474 from mlir.<dialect> import ConcreteAttr, ConcreteType
491 from mlir.<dialect> import ConcreteAttr, ConcreteType
912 Each dialect with a mapping to python requires that an appropriate
915 includes the boilerplate and actual dialect specific `td` file. An example, for
931 mlir-tblgen -gen-python-op-bindings -bind-dialect={DIALECT_NAMESPACE} \
1022 `_{DIALECT_NAMESPACE}_ops_gen.py` for each dialect with Python bindings. It is
1095 ## Providing Python bindings for a dialect
1097 Python bindings are designed to support MLIR’s open dialect ecosystem. A dialect
1116 -bind-dialect=<dialect-namespace>` generates the Python API from the declarative
1123 `_<dialect-namespace>_ops_gen.py` by convention. The generated operation classes
1127 `python/mlir/dialects/<dialect-namespace>.py` or a
1128 `python/mlir/dialects/<dialect-namespace>/__init__.py` file must be created and
1130 mlir.dialects.<dialect-namespace>` in Python.
1150 The attribute and type bindings for a dialect can be located in
1156 from the main dialect file, i.e. `python/mlir/dialects/<dialect-namespace>.py`
1157 or `python/mlir/dialects/<dialect-namespace>/__init__.py`, to ensure the types
1158 are available when the dialect is loaded from Python.
1171 which can be `import`ed  from the main dialect file, i.e.
1172 `python/mlir/dialects/<dialect-namespace>.py` or
1173 `python/mlir/dialects/<dialect-namespace>/__init__.py`, or from a separate
1175 `python/mlir/dialects/<dialect-namespace>/passes.py` if it is undesirable to
1176 make the passes available along with the dialect.
1189 loaded along with the dialect.