@@ -14,19 +14,20 @@ The tool is bundled with the MLIR Python bindings. To use from the CMake build
1414tree, MLIR must be build with Python bindings enabled
1515(` -DMLIR_ENALBE_BINDINGS_PYTHON=ON ` ). Then add the ` python ` directory in the
1616build tree to your ` PYTHONPATH ` environment variable (i.e. `export
17- PYTHONPATH=$PWD/build/python `). Optionally, use an installed MLIR package, if
18- available, to avoid building.
17+ PYTHONPATH=$PWD/build/tools/mlir/python_packages/mlir_core `). Optionally, use an
18+ installed MLIR package, if available, to avoid building.
1919
2020``` shell
2121# Dump the `core_named_ops.py` module as YAML.
2222python -m mlir.dialects.linalg.opdsl.dump_oplib .ops.core_named_ops
2323```
2424
25- The tool is meant for use during both development and runtime, but not as a
26- build tool of the core compiler: in order to export static named op definitions
27- to be built as part of the compiler, the corresponding Linalg dialect YAML file
28- must be updated and reviewed. TODO: Develop a script to automate op updates to
29- these files.
25+ Alternatively, run the ` $PWD/build/bin/update_core_linalg_named_ops.sh ` script,
26+ which is available after building the ` mlir-linalg-ods-gen ` target. The tool is
27+ meant for use during both development and runtime, but not as a build tool of
28+ the core compiler: in order to export static named op definitions to be built as
29+ part of the compiler, the corresponding Linalg dialect YAML file must be updated
30+ and reviewed. TODO: Develop a script to automate op updates to these files.
3031
3132## Language Guide
3233
0 commit comments